Switching bandwidth parts based on beam failure recovery configuration

ABSTRACT

A wireless device switches from a first downlink bandwidth part (BWP) to a second downlink BWP identified with a downlink BWP index. Based on the second downlink BWP being configured with beam failure recovery (BFR), a first uplink BWP is switched to a second uplink BWP identified with a uplink BWP index that is the same as the downlink BWP index. The second downlink BWP is switched to a third downlink BWP. Based on the third downlink BWP not being configured with BFR, the second uplink BWP is kept as an active uplink BWP.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/529,981, filed Aug. 2, 2019, which claims the benefit of U.S.Provisional Application No. 62/714,320, filed Aug. 3, 2018, which ishereby incorporated by reference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 2A is a diagram of an example user plane protocol stack as per anaspect of an embodiment of the present disclosure.

FIG. 2B is a diagram of an example control plane protocol stack as peran aspect of an embodiment of the present disclosure.

FIG. 3 is a diagram of an example wireless device and two base stationsas per an aspect of an embodiment of the present disclosure.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals as per an aspect of an embodiment of the presentdisclosure.

FIG. 5B is a diagram of an example downlink channel mapping and exampledownlink physical signals as per an aspect of an embodiment of thepresent disclosure.

FIG. 6 is a diagram depicting an example transmission time or receptiontime for a carrier as per an aspect of an embodiment of the presentdisclosure.

FIG. 7A and FIG. 7B are diagrams depicting example sets of OFDMsubcarriers as per an aspect of an embodiment of the present disclosure.

FIG. 8 is a diagram depicting example OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 9A is a diagram depicting an example CSI-RS and/or SS blocktransmission in a multi-beam system.

FIG. 9B is a diagram depicting an example downlink beam managementprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 10 is an example diagram of configured BWPs as per an aspect of anembodiment of the present disclosure.

FIG. 11A, and FIG. 11B are diagrams of an example multi connectivity asper an aspect of an embodiment of the present disclosure.

FIG. 12 is a diagram of an example random access procedure as per anaspect of an embodiment of the present disclosure.

FIG. 13 is a structure of example MAC entities as per an aspect of anembodiment of the present disclosure.

FIG. 14 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 15 is a diagram of example RRC states as per an aspect of anembodiment of the present disclosure.

FIG. 16A and FIG. 16B are examples of downlink beam failure as per anaspect of an embodiment of the present disclosure.

FIG. 17 is an example flowchart of a downlink beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 18 is an example of downlink beam failure instance indication asper an aspect of an embodiment of the present disclosure.

FIG. 19 is an example of bandwidth part operation as per an aspect of anembodiment of the present disclosure.

FIG. 20 is an example of bandwidth part operation as per an aspect of anembodiment of the present disclosure.

FIG. 21A and FIG. 21B are examples of bandwidth part (BWP) switchingoperation as per an aspect of an embodiment of the present disclosure.

FIG. 22 is an example flowchart of BWP switching operation as per anaspect of an embodiment of the present disclosure.

FIG. 23 shows an example of a BWP linkage in beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 24 shows an example of a BWP linkage in beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 25 shows an example of a BWP linkage in beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 26 shows an example of a BWP linkage in beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 27 shows an example flowchart of a BWP linkage in beam failurerecovery procedure as per an aspect of an embodiment of the presentdisclosure.

FIG. 28 shows an example of a BWP linkage in beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 29 shows an example of a BWP linkage in beam failure recoveryprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 30 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable operation of beamfailure recovery procedure. Embodiments of the technology disclosedherein may be employed in the technical field of multicarriercommunication systems. More particularly, the embodiments of thetechnology disclosed herein may relate to beam failure recoveryprocedure in a multicarrier communication system.

The following Acronyms are used throughout the present disclosure:

3GPP 3rd Generation Partnership Project

5GC 5G Core Network

ACK Acknowledgement

AMF Access and Mobility Management Function

ARQ Automatic Repeat Request

AS Access Stratum

ASIC Application-Specific Integrated Circuit

BA Bandwidth Adaptation

BCCH Broadcast Control Channel

BCH Broadcast Channel

BPSK Binary Phase Shift Keying

BWP Bandwidth Part

CA Carrier Aggregation

CC Component Carrier

CCCH Common Control CHannel

CDMA Code Division Multiple Access

CN Core Network

CP Cyclic Prefix

CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex

C-RNTI Cell-Radio Network Temporary Identifier

CS Configured Scheduling

CSI Channel State Information

CSI-RS Channel State Information-Reference Signal

CQI Channel Quality Indicator

CSS Common Search Space

CU Central Unit

DC Dual Connectivity

DCCH Dedicated Control Channel

DCI Downlink Control Information

DL Downlink

DL-SCH Downlink Shared CHannel

DM-RS DeModulation Reference Signal

DRB Data Radio Bearer

DRX Discontinuous Reception

DTCH Dedicated Traffic Channel

DU Distributed Unit

EPC Evolved Packet Core

E-UTRA Evolved UMTS Terrestrial Radio Access

E-UTRAN Evolved-Universal Terrestrial Radio Access Network

FDD Frequency Division Duplex

FPGA Field Programmable Gate Arrays

F1-C F1-Control plane

F1-U F1-User plane

gNB next generation Node B

HARQ Hybrid Automatic Repeat reQuest

HDL Hardware Description Languages

IE Information Element

IP Internet Protocol

LCID Logical Channel Identifier

LTE Long Term Evolution

MAC Media Access Control

MCG Master Cell Group

MCS Modulation and Coding Scheme

MeNB Master evolved Node B

MIB Master Information Block

MME Mobility Management Entity

MN Master Node

NACK Negative Acknowledgement

NAS Non-Access Stratum

NG CP Next Generation Control Plane

NGC Next Generation Core

NG-C NG-Control plane

ng-eNB next generation evolved Node B

NG-U NG-User plane

NR New Radio

NR MAC New Radio MAC

NR PDCP New Radio PDCP

NR PHY New Radio PHYsical

NR RLC New Radio RLC

NR RRC New Radio RRC

NSSAI Network Slice Selection Assistance Information

O&M Operation and Maintenance

OFDM orthogonal Frequency Division Multiplexing

PBCH Physical Broadcast CHannel

PCC Primary Component Carrier

PCCH Paging Control CHannel

PCell Primary Cell

PCH Paging CHannel

PDCCH Physical Downlink Control CHannel

PDCP Packet Data Convergence Protocol

PDSCH Physical Downlink Shared CHannel

PDU Protocol Data Unit

PHICH Physical HARQ Indicator CHannel

PHY PHYsical

PLMN Public Land Mobile Network

PMI Precoding Matrix Indicator

PRACH Physical Random Access CHannel

PRB Physical Resource Block

PSCell Primary Secondary Cell

PSS Primary Synchronization Signal

pTAG primary Timing Advance Group

PT-RS Phase Tracking Reference Signal

PUCCH Physical Uplink Control CHannel

PUSCH Physical Uplink Shared CHannel

QAM Quadrature Amplitude Modulation

QFI Quality of Service Indicator

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

RA Random Access

RACH Random Access CHannel

RAN Radio Access Network

RAT Radio Access Technology

RA-RNTI Random Access-Radio Network Temporary Identifier

RB Resource Blocks

RBG Resource Block Groups

RI Rank indicator

RLC Radio Link Control

RLM Radio Link Monitoring

RRC Radio Resource Control

RS Reference Signal

RSRP Reference Signal Received Power

SCC Secondary Component Carrier

SCell Secondary Cell

SCG Secondary Cell Group

SC-FDMA Single Carrier-Frequency Division Multiple Access

SDAP Service Data Adaptation Protocol

SDU Service Data Unit

SeNB Secondary evolved Node B

SFN System Frame Number

S-GW Serving GateWay

SI System Information

SIB System Information Block

SMF Session Management Function

SN Secondary Node

SpCell Special Cell

SRB Signaling Radio Bearer

SRS Sounding Reference Signal

SS Synchronization Signal

SSS Secondary Synchronization Signal

sTAG secondary Timing Advance Group

TA Timing Advance

TAG Timing Advance Group

TAI Tracking Area Identifier

TAT Time Alignment Timer

TB Transport Block

TC-RNTI Temporary Cell-Radio Network Temporary Identifier

TDD Time Division Duplex

TDMA Time Division Multiple Access

TTI Transmission Time Interval

UCI Uplink Control Information

UE User Equipment

UL Uplink

UL-SCH Uplink Shared CHannel

UPF User Plane Function

UPGW User Plane Gateway

VHDL VHSIC Hardware Description Language

Xn-C Xn-Control plane

Xn-U Xn-User plane

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CodeDivision Multiple Access (CDMA), Orthogonal Frequency Division MultipleAccess (OFDMA), Time Division Multiple Access (TDMA), Wavelettechnologies, and/or the like. Hybrid transmission mechanisms such asTDMA/CDMA, and OFDM/CDMA may also be employed. Various modulationschemes may be applied for signal transmission in the physical layer.Examples of modulation schemes include, but are not limited to: phase,amplitude, code, a combination of these, and/or the like. An exampleradio transmission method may implement Quadrature Amplitude Modulation(QAM) using Binary Phase Shift Keying (BPSK), Quadrature Phase ShiftKeying (QPSK), 16-QAM, 64-QAM, 256-QAM, 1024-QAM, and/or the like.Physical radio transmission may be enhanced by dynamically orsemi-dynamically changing the modulation and coding scheme depending ontransmission requirements and radio conditions.

FIG. 1 is an example Radio Access Network (RAN) architecture as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, a RAN node may be a next generation Node B (gNB) (e.g.120A, 120B) providing New Radio (NR) user plane and control planeprotocol terminations towards a first wireless device (e.g. 110A). In anexample, a RAN node may be a next generation evolved Node B (ng-eNB)(e.g. 120C, 120D), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device (e.g. 110B). The first wireless device maycommunicate with a gNB over a Uu interface. The second wireless devicemay communicate with a ng-eNB over a Uu interface.

A gNB or an ng-eNB may host functions such as radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of UEs inRRC_INACTIVE state, distribution function for Non-Access Stratum (NAS)messages, RAN sharing, dual connectivity or tight interworking betweenNR and E-UTRA.

In an example, one or more gNBs and/or one or more ng-eNBs may beinterconnected with each other by means of Xn interface. A gNB or anng-eNB may be connected by means of NG interfaces to 5G Core Network(5GC). In an example, 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g. 130A or 130B). A gNB or an ng-eNB may beconnected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g. non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide functions such asNG interface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, configurationtransfer or warning message transmission.

In an example, a UPF may host functions such as anchor point forintra-/inter-Radio Access Technology (RAT) mobility (when applicable),external PDU session point of interconnect to data network, packetrouting and forwarding, packet inspection and user plane part of policyrule enforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, QoS handling for user plane, e.g. packetfiltering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplinktraffic verification (e.g. Service Data Flow (SDF) to QoS flow mapping),downlink packet buffering and/or downlink data notification triggering.

In an example, an AMF may host functions such as NAS signalingtermination, NAS signaling security, Access Stratum (AS) securitycontrol, inter Core Network (CN) node signaling for mobility between3^(rd) Generation Partnership Project (3GPP) access networks, idle modeUE reachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (subscription and policies),support of network slicing and/or Session Management Function (SMF)selection.

FIG. 2A is an example user plane protocol stack, where Service DataAdaptation Protocol (SDAP) (e.g. 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g. 212 and 222), Radio Link Control (RLC) (e.g. 213and 223) and Media Access Control (MAC) (e.g. 214 and 224) sublayers andPhysical (PHY) (e.g. 215 and 225) layer may be terminated in wirelessdevice (e.g. 110) and gNB (e.g. 120) on the network side. In an example,a PHY layer provides transport services to higher layers (e.g. MAC, RRC,etc.). In an example, services and functions of a MAC sublayer maycomprise mapping between logical channels and transport channels,multiplexing/demultiplexing of MAC Service Data Units (SDUs) belongingto one or different logical channels into/from Transport Blocks (TBs)delivered to/from the PHY layer, scheduling information reporting, errorcorrection through Hybrid Automatic Repeat request (HARQ) (e.g. one HARQentity per carrier in case of Carrier Aggregation (CA)), priorityhandling between UEs by means of dynamic scheduling, priority handlingbetween logical channels of one UE by means of logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. In an example, mappingrestrictions in a logical channel prioritization may control whichnumerology and/or transmission timing a logical channel may use. In anexample, an RLC sublayer may supports transparent mode (TM),unacknowledged mode (UM) and acknowledged mode (AM) transmission modes.The RLC configuration may be per logical channel with no dependency onnumerologies and/or Transmission Time Interval (TTI) durations. In anexample, Automatic Repeat Request (ARQ) may operate on any of thenumerologies and/or TTI durations the logical channel is configuredwith. In an example, services and functions of the PDCP layer for theuser plane may comprise sequence numbering, header compression anddecompression, transfer of user data, reordering and duplicatedetection, PDCP PDU routing (e.g. in case of split bearers),retransmission of PDCP SDUs, ciphering, deciphering and integrityprotection, PDCP SDU discard, PDCP re-establishment and data recoveryfor RLC AM, and/or duplication of PDCP PDUs. In an example, services andfunctions of SDAP may comprise mapping between a QoS flow and a dataradio bearer. In an example, services and functions of SDAP may comprisemapping Quality of Service Indicator (QFI) in DL and UL packets. In anexample, a protocol entity of SDAP may be configured for an individualPDU session.

FIG. 2B is an example control plane protocol stack where PDCP (e.g. 233and 242), RLC (e.g. 234 and 243) and MAC (e.g. 235 and 244) sublayersand PHY (e.g. 236 and 245) layer may be terminated in wireless device(e.g. 110) and gNB (e.g. 120) on a network side and perform service andfunctions described above. In an example, RRC (e.g. 232 and 241) may beterminated in a wireless device and a gNB on a network side. In anexample, services and functions of RRC may comprise broadcast of systeminformation related to AS and NAS, paging initiated by 5GC or RAN,establishment, maintenance and release of an RRC connection between theUE and RAN, security functions including key management, establishment,configuration, maintenance and release of Signaling Radio Bearers (SRBs)and Data Radio Bearers (DRBs), mobility functions, QoS managementfunctions, UE measurement reporting and control of the reporting,detection of and recovery from radio link failure, and/or NAS messagetransfer to/from NAS from/to a UE. In an example, NAS control protocol(e.g. 231 and 251) may be terminated in the wireless device and AMF(e.g. 130) on a network side and may perform functions such asauthentication, mobility management between a UE and a AMF for 3GPPaccess and non-3GPP access, and session management between a UE and aSMF for 3GPP access and non-3GPP access.

In an example, a base station may configure a plurality of logicalchannels for a wireless device. A logical channel in the plurality oflogical channels may correspond to a radio bearer and the radio bearermay be associated with a QoS requirement. In an example, a base stationmay configure a logical channel to be mapped to one or moreTTIs/numerologies in a plurality of TTIs/numerologies. The wirelessdevice may receive a Downlink Control Information (DCI) via PhysicalDownlink Control CHannel (PDCCH) indicating an uplink grant. In anexample, the uplink grant may be for a first TTI/numerology and mayindicate uplink resources for transmission of a transport block. Thebase station may configure each logical channel in the plurality oflogical channels with one or more parameters to be used by a logicalchannel prioritization procedure at the MAC layer of the wirelessdevice. The one or more parameters may comprise priority, prioritizedbit rate, etc. A logical channel in the plurality of logical channelsmay correspond to one or more buffers comprising data associated withthe logical channel. The logical channel prioritization procedure mayallocate the uplink resources to one or more first logical channels inthe plurality of logical channels and/or one or more MAC ControlElements (CEs). The one or more first logical channels may be mapped tothe first TTI/numerology. The MAC layer at the wireless device maymultiplex one or more MAC CEs and/or one or more MAC SDUs (e.g., logicalchannel) in a MAC PDU (e.g., transport block). In an example, the MACPDU may comprise a MAC header comprising a plurality of MAC sub-headers.A MAC sub-header in the plurality of MAC sub-headers may correspond to aMAC CE or a MAC SUD (logical channel) in the one or more MAC CEs and/orone or more MAC SDUs. In an example, a MAC CE or a logical channel maybe configured with a Logical Channel IDentifier (LCID). In an example,LCID for a logical channel or a MAC CE may be fixed/pre-configured. Inan example, LCID for a logical channel or MAC CE may be configured forthe wireless device by the base station. The MAC sub-headercorresponding to a MAC CE or a MAC SDU may comprise LCID associated withthe MAC CE or the MAC SDU.

In an example, a base station may activate and/or deactivate and/orimpact one or more processes (e.g., set values of one or more parametersof the one or more processes or start and/or stop one or more timers ofthe one or more processes) at the wireless device by employing one ormore MAC commands. The one or more MAC commands may comprise one or moreMAC control elements. In an example, the one or more processes maycomprise activation and/or deactivation of PDCP packet duplication forone or more radio bearers. The base station may transmit a MAC CEcomprising one or more fields, the values of the fields indicatingactivation and/or deactivation of PDCP duplication for the one or moreradio bearers. In an example, the one or more processes may compriseChannel State Information (CSI) transmission of on one or more cells.The base station may transmit one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells. Inan example, the one or more processes may comprise activation ordeactivation of one or more secondary cells. In an example, the basestation may transmit a MA CE indicating activation or deactivation ofone or more secondary cells. In an example, the base station maytransmit one or more MAC CEs indicating starting and/or stopping one ormore Discontinuous Reception (DRX) timers at the wireless device. In anexample, the base station may transmit one or more MAC CEs indicatingone or more timing advance values for one or more Timing Advance Groups(TAGs).

FIG. 3 is a block diagram of base stations (base station 1, 120A, andbase station 2, 120B) and a wireless device 110. A wireless device maybe called an UE. A base station may be called a NB, eNB, gNB, and/orng-eNB. In an example, a wireless device and/or a base station may actas a relay node. The base station 1, 120A, may comprise at least onecommunication interface 320A (e.g. a wireless modem, an antenna, a wiredmodem, and/or the like), at least one processor 321A, and at least oneset of program code instructions 323A stored in non-transitory memory322A and executable by the at least one processor 321A. The base station2, 120B, may comprise at least one communication interface 320B, atleast one processor 321B, and at least one set of program codeinstructions 323B stored in non-transitory memory 322B and executable bythe at least one processor 321B.

A base station may comprise many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may comprise many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At Radio Resource Control (RRC)connection establishment/re-establishment/handover, one serving cell mayprovide the NAS (non-access stratum) mobility information (e.g. TrackingArea Identifier (TAI)). At RRC connection re-establishment/handover, oneserving cell may provide the security input. This cell may be referredto as the Primary Cell (PCell). In the downlink, a carrier correspondingto the PCell may be a DL Primary Component Carrier (PCC), while in theuplink, a carrier may be an UL PCC. Depending on wireless devicecapabilities, Secondary Cells (SCells) may be configured to formtogether with a PCell a set of serving cells. In a downlink, a carriercorresponding to an SCell may be a downlink secondary component carrier(DL SCC), while in an uplink, a carrier may be an uplink secondarycomponent carrier (UL SCC). An SCell may or may not have an uplinkcarrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to one cell. The cell ID or cell index may alsoidentify the downlink carrier or uplink carrier of the cell (dependingon the context it is used). In the disclosure, a cell ID may be equallyreferred to a carrier ID, and a cell index may be referred to a carrierindex. In an implementation, a physical cell ID or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted on a downlink carrier. A cell index may be determinedusing RRC messages. For example, when the disclosure refers to a firstphysical cell ID for a first downlink carrier, the disclosure may meanthe first physical cell ID is for a cell comprising the first downlinkcarrier. The same concept may apply to, for example, carrier activation.When the disclosure indicates that a first carrier is activated, thespecification may equally mean that a cell comprising the first carrieris activated.

A base station may transmit to a wireless device one or more messages(e.g. RRC messages) comprising a plurality of configuration parametersfor one or more cells. One or more cells may comprise at least oneprimary cell and at least one secondary cell. In an example, an RRCmessage may be broadcasted or unicasted to the wireless device. In anexample, configuration parameters may comprise common parameters anddedicated parameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and NAS; paginginitiated by 5GC and/or NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and NG-RAN, whichmay comprise at least one of addition, modification and release ofcarrier aggregation; or addition, modification, and/or release of dualconnectivity in NR or between E-UTRA and NR. Services and/or functionsof an RRC sublayer may further comprise at least one of securityfunctions comprising key management; establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and/orData Radio Bearers (DRBs); mobility functions which may comprise atleast one of a handover (e.g. intra NR mobility or inter-RAT mobility)and a context transfer; or a wireless device cell selection andreselection and control of cell selection and reselection. Servicesand/or functions of an RRC sublayer may further comprise at least one ofQoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; or NAS message transfer to/from a core network entity (e.g.AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive stateand/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection/re-selection; monitoring/receiving a paging for mobileterminated data initiated by 5GC; paging for mobile terminated data areamanaged by 5GC; or DRX for CN paging configured via NAS. In anRRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection/re-selection;monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-basednotification area (RNA) managed by NG-RAN; or DRX for RAN/CN pagingconfigured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, abase station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (bothC/U-planes) for the wireless device; and/or store a UE AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g. NG-RAN) may perform at least one of: establishment of5GC-NG-RAN connection (both C/U-planes) for the wireless device; storinga UE AS context for the wireless device; transmit/receive of unicastdata to/from the wireless device; or network-controlled mobility basedon measurement results received from the wireless device. In anRRC_Connected state of a wireless device, an NG-RAN may know a cell thatthe wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and information foracquiring any other SI broadcast periodically or provisioned on-demand,i.e. scheduling information. The other SI may either be broadcast, or beprovisioned in a dedicated manner, either triggered by a network or uponrequest from a wireless device. A minimum SI may be transmitted via twodifferent downlink channels using different messages (e.g.MasterInformationBlock and SystemInformationBlockType1). Another SI maybe transmitted via SystemInformationBlockType2. For a wireless device inan RRC_Connected state, dedicated RRC signaling may be employed for therequest and delivery of the other SI. For the wireless device in theRRC_Idle state and/or the RRC_Inactive state, the request may trigger arandom-access procedure.

A wireless device may report its radio access capability informationwhich may be static. A base station may request what capabilities for awireless device to report based on band information. When allowed by anetwork, a temporary capability restriction request may be sent by thewireless device to signal the limited availability of some capabilities(e.g. due to hardware sharing, interference or overheating) to the basestation. The base station may confirm or reject the request. Thetemporary capability restriction may be transparent to 5GC (e.g., staticcapabilities may be stored in 5GC).

When CA is configured, a wireless device may have an RRC connection witha network. At RRC connection establishment/re-establishment/handoverprocedure, one serving cell may provide NAS mobility information, and atRRC connection re-establishment/handover, one serving cell may provide asecurity input. This cell may be referred to as the PCell. Depending onthe capabilities of the wireless device, SCells may be configured toform together with the PCell a set of serving cells. The configured setof serving cells for the wireless device may comprise one PCell and oneor more SCells.

The reconfiguration, addition and removal of SCells may be performed byRRC. At intra-NR handover, RRC may also add, remove, or reconfigureSCells for usage with the target PCell. When adding a new SCell,dedicated RRC signaling may be employed to send all required systeminformation of the SCell i.e. while in connected mode, wireless devicesmay not need to acquire broadcasted system information directly from theSCells.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells and cell groups). As part of the RRCconnection reconfiguration procedure, NAS dedicated information may betransferred from the network to the wireless device. TheRRCConnectionReconfiguration message may be a command to modify an RRCconnection. It may convey information for measurement configuration,mobility control, radio resource configuration (e.g. RBs, MAC mainconfiguration and physical channel configuration) comprising anyassociated dedicated NAS information and security configuration. If thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList, the wireless device may perform an SCell release. Ifthe received RRC Connection Reconfiguration message includes thesCellToAddModList, the wireless device may perform SCell additions ormodification.

An RRC connection establishment (or reestablishment, resume) proceduremay be to establish (or reestablish, resume) an RRC connection. an RRCconnection establishment procedure may comprise SRB1 establishment. TheRRC connection establishment procedure may be used to transfer theinitial NAS dedicated information/message from a wireless device toE-UTRAN. The RRCConnectionReestablishment message may be used tore-establish SRB1.

A measurement report procedure may be to transfer measurement resultsfrom a wireless device to NG-RAN. The wireless device may initiate ameasurement report procedure after successful security activation. Ameasurement report message may be employed to transmit measurementresults.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g. a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 stored in non-transitory memory 315 and executable bythe at least one processor 314. The wireless device 110 may furthercomprise at least one of at least one speaker/microphone 311, at leastone keypad 312, at least one display/touchpad 313, at least one powersource 317, at least one global positioning system (GPS) chipset 318,and other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding/processing, data processing, powercontrol, input/output processing, and/or any other functionality thatmay enable the wireless device 110, the base station 1 120A and/or thebase station 2 120B to operate in a wireless environment.

The processor 314 of the wireless device 110 may be connected to thespeaker/microphone 311, the keypad 312, and/or the display/touchpad 313.The processor 314 may receive user input data from and/or provide useroutput data to the speaker/microphone 311, the keypad 312, and/or thedisplay/touchpad 313. The processor 314 in the wireless device 110 mayreceive power from the power source 317 and/or may be configured todistribute the power to the other components in the wireless device 110.The power source 317 may comprise at least one of one or more dry cellbatteries, solar cells, fuel cells, and the like. The processor 314 maybe connected to the GPS chipset 318. The GPS chipset 318 may beconfigured to provide geographic location information of the wirelessdevice 110.

The processor 314 of the wireless device 110 may further be connected toother peripherals 319, which may comprise one or more software and/orhardware modules that provide additional features and/orfunctionalities. For example, the peripherals 319 may comprise at leastone of an accelerometer, a satellite transceiver, a digital camera, auniversal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, and thelike.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110 via a wireless link 330A and/or a wireless link 330Brespectively. In an example, the communication interface 320A of thebase station 1, 120A, may communicate with the communication interface320B of the base station 2 and other RAN and core network nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110 and/or thebase station 2 120B and the wireless device 110 may be configured tosend and receive transport blocks via the wireless link 330A and/or viathe wireless link 330B, respectively. The wireless link 330A and/or thewireless link 330B may employ at least one frequency carrier. Accordingto some of various aspects of embodiments, transceiver(s) may beemployed. A transceiver may be a device that comprises both atransmitter and a receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in thecommunication interface 310, 320A, 320B and the wireless link 330A, 330Bare illustrated in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A,FIG. 7B, FIG. 8, and associated text.

In an example, other nodes in a wireless network (e.g. AMF, UPF, SMF,etc.) may comprise one or more communication interfaces, one or moreprocessors, and memory storing instructions.

A node (e.g. wireless device, base station, AMF, SMF, UPF, servers,switches, antennas, and/or the like) may comprise one or moreprocessors, and memory storing instructions that when executed by theone or more processors causes the node to perform certain processesand/or functions. Example embodiments may enable operation ofsingle-carrier and/or multi-carrier communications. Other exampleembodiments may comprise a non-transitory tangible computer readablemedia comprising instructions executable by one or more processors tocause operation of single-carrier and/or multi-carrier communications.Yet other example embodiments may comprise an article of manufacturethat comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a node to enable operation ofsingle-carrier and/or multi-carrier communications. The node may includeprocessors, memory, interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and code stored in and/or incommunication with a memory device to implement connections, electronicdevice operations, protocol(s), protocol layers, communication drivers,device drivers, hardware operations, combinations thereof, and/or thelike.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 4A shows an example uplink transmitter forat least one physical channel. A baseband signal representing a physicaluplink shared channel may perform one or more functions. The one or morefunctions may comprise at least one of: scrambling; modulation ofscrambled bits to generate complex-valued symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; transform precoding to generate complex-valued symbols;precoding of the complex-valued symbols; mapping of precodedcomplex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 4A. These functions are illustrated as examples andit is anticipated that other mechanisms may be implemented in variousembodiments.

An example structure for modulation and up-conversion to the carrierfrequency of the complex-valued SC-FDMA or CP-OFDM baseband signal foran antenna port and/or the complex-valued Physical Random Access CHannel(PRACH) baseband signal is shown in FIG. 4B. Filtering may be employedprior to transmission.

An example structure for downlink transmissions is shown in FIG. 4C. Thebaseband signal representing a downlink physical channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

In an example, a gNB may transmit a first symbol and a second symbol onan antenna port, to a wireless device. The wireless device may infer thechannel (e.g., fading gain, multipath delay, etc.) for conveying thesecond symbol on the antenna port, from the channel for conveying thefirst symbol on the antenna port. In an example, a first antenna portand a second antenna port may be quasi co-located if one or morelarge-scale properties of the channel over which a first symbol on thefirst antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;doppler spread; doppler shift; average gain; average delay; and/orspatial Receiving (Rx) parameters.

An example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for an antenna port is shown in FIG.4D. Filtering may be employed prior to transmission.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals. FIG. 5B is a diagram of an example downlinkchannel mapping and a downlink physical signals. In an example, aphysical layer may provide one or more information transfer services toa MAC and/or one or more higher layers. For example, the physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and with what characteristics data are transferred over theradio interface.

In an example embodiment, a radio network may comprise one or moredownlink and/or uplink transport channels. For example, a diagram inFIG. 5A shows example uplink transport channels comprising Uplink-SharedCHannel (UL-SCH) 501 and Random Access CHannel (RACH) 502. A diagram inFIG. 5B shows example downlink transport channels comprisingDownlink-Shared CHannel (DL-SCH) 511, Paging CHannel (PCH) 512, andBroadcast CHannel (BCH) 513. A transport channel may be mapped to one ormore corresponding physical channels. For example, UL-SCH 501 may bemapped to Physical Uplink Shared CHannel (PUSCH) 503. RACH 502 may bemapped to PRACH 505. DL-SCH 511 and PCH 512 may be mapped to PhysicalDownlink Shared CHannel (PDSCH) 514. BCH 513 may be mapped to PhysicalBroadcast CHannel (PBCH) 516.

There may be one or more physical channels without a correspondingtransport channel. The one or more physical channels may be employed forUplink Control Information (UCI) 509 and/or Downlink Control Information(DCI) 517. For example, Physical Uplink Control CHannel (PUCCH) 504 maycarry UCI 509 from a UE to a base station. For example, PhysicalDownlink Control CHannel (PDCCH) 515 may carry DCI 517 from a basestation to a UE. NR may support UCI 509 multiplexing in PUSCH 503 whenUCI 509 and PUSCH 503 transmissions may coincide in a slot at least inpart. The UCI 509 may comprise at least one of CSI, Acknowledgement(ACK)/Negative Acknowledgement (NACK), and/or scheduling request. TheDCI 517 on PDCCH 515 may indicate at least one of following: one or moredownlink assignments and/or one or more uplink scheduling grants

In uplink, a UE may transmit one or more Reference Signals (RSs) to abase station. For example, the one or more RSs may be at least one ofDemodulation-RS (DM-RS) 506, Phase Tracking-RS (PT-RS) 507, and/orSounding RS (SRS) 508. In downlink, a base station may transmit (e.g.,unicast, multicast, and/or broadcast) one or more RSs to a UE. Forexample, the one or more RSs may be at least one of PrimarySynchronization Signal (PSS)/Secondary Synchronization Signal (SSS) 521,CSI-RS 522, DM-RS 523, and/or PT-RS 524.

In an example, a UE may transmit one or more uplink DM-RSs 506 to a basestation for channel estimation, for example, for coherent demodulationof one or more uplink physical channels (e.g., PUSCH 503 and/or PUCCH504). For example, a UE may transmit a base station at least one uplinkDM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at least oneuplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. In an example, a base station mayconfigure a UE with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to transmit at one or more symbols of a PUSCH and/or PUCCH. Abase station may semi-statistically configure a UE with a maximum numberof front-loaded DM-RS symbols for PUSCH and/or PUCCH. For example, a UEmay schedule a single-symbol DM-RS and/or double symbol DM-RS based on amaximum number of front-loaded DM-RS symbols, wherein a base station mayconfigure the UE with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, e.g., at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

In an example, whether uplink PT-RS 507 is present or not may depend ona RRC configuration. For example, a presence of uplink PT-RS may beUE-specifically configured. For example, a presence and/or a pattern ofuplink PT-RS 507 in a scheduled resource may be UE-specificallyconfigured by a combination of RRC signaling and/or association with oneor more parameters employed for other purposes (e.g., Modulation andCoding Scheme (MCS)) which may be indicated by DCI. When configured, adynamic presence of uplink PT-RS 507 may be associated with one or moreDCI parameters comprising at least MCS. A radio network may supportplurality of uplink PT-RS densities defined in time/frequency domain.When present, a frequency domain density may be associated with at leastone configuration of a scheduled bandwidth. A UE may assume a sameprecoding for a DMRS port and a PT-RS port. A number of PT-RS ports maybe fewer than a number of DM-RS ports in a scheduled resource. Forexample, uplink PT-RS 507 may be confined in the scheduledtime/frequency duration for a UE.

In an example, a UE may transmit SRS 508 to a base station for channelstate estimation to support uplink channel dependent scheduling and/orlink adaptation. For example, SRS 508 transmitted by a UE may allow fora base station to estimate an uplink channel state at one or moredifferent frequencies. A base station scheduler may employ an uplinkchannel state to assign one or more resource blocks of good quality foran uplink PUSCH transmission from a UE. A base station maysemi-statistically configure a UE with one or more SRS resource sets.For an SRS resource set, a base station may configure a UE with one ormore SRS resources. An SRS resource set applicability may be configuredby a higher layer (e.g., RRC) parameter. For example, when a higherlayer parameter indicates beam management, a SRS resource in each of oneor more SRS resource sets may be transmitted at a time instant. A UE maytransmit one or more SRS resources in different SRS resource setssimultaneously. A new radio network may support aperiodic, periodicand/or semi-persistent SRS transmissions. A UE may transmit SRSresources based on one or more trigger types, wherein the one or moretrigger types may comprise higher layer signaling (e.g., RRC) and/or oneor more DCI formats (e.g., at least one DCI format may be employed for aUE to select at least one of one or more configured SRS resource sets.An SRS trigger type 0 may refer to an SRS triggered based on a higherlayer signaling. An SRS trigger type 1 may refer to an SRS triggeredbased on one or more DCI formats. In an example, when PUSCH 503 and SRS508 are transmitted in a same slot, a UE may be configured to transmitSRS 508 after a transmission of PUSCH 503 and corresponding uplink DM-RS506.

In an example, a base station may semi-statistically configure a UE withone or more SRS configuration parameters indicating at least one offollowing: a SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, a SRS bandwidth, afrequency hopping bandwidth, a cyclic shift, and/or a SRS sequence ID.

In an example, in a time domain, an SS/PBCH block may comprise one ormore OFDM symbols (e.g., 4 OFDM symbols numbered in increasing orderfrom 0 to 3) within the SS/PBCH block. An SS/PBCH block may comprisePSS/SSS 521 and PBCH 516. In an example, in the frequency domain, anSS/PBCH block may comprise one or more contiguous subcarriers (e.g., 240contiguous subcarriers with the subcarriers numbered in increasing orderfrom 0 to 239) within the SS/PBCH block. For example, a PSS/SSS 521 mayoccupy 1 OFDM symbol and 127 subcarriers. For example, PBCH 516 may spanacross 3 OFDM symbols and 240 subcarriers. A UE may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, e.g., with respect to Doppler spread, Doppler shift, averagegain, average delay, and spatial Rx parameters. A UE may not assumequasi co-location for other SS/PBCH block transmissions. A periodicityof an SS/PBCH block may be configured by a radio network (e.g., by anRRC signaling) and one or more time locations where the SS/PBCH blockmay be sent may be determined by sub-carrier spacing. In an example, aUE may assume a band-specific sub-carrier spacing for an SS/PBCH blockunless a radio network has configured a UE to assume a differentsub-carrier spacing.

In an example, downlink CSI-RS 522 may be employed for a UE to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of downlink CSI-RS 522.For example, a base station may semi-statistically configure and/orreconfigure a UE with periodic transmission of downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated ad/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation ofCSI-RS resource may be triggered dynamically. In an example, CSI-RSconfiguration may comprise one or more parameters indicating at least anumber of antenna ports. For example, a base station may configure a UEwith 32 ports. A base station may semi-statistically configure a UE withone or more CSI-RS resource sets. One or more CSI-RS resources may beallocated from one or more CSI-RS resource sets to one or more UEs. Forexample, a base station may semi-statistically configure one or moreparameters indicating CSI RS resource mapping, for example, time-domainlocation of one or more CSI-RS resources, a bandwidth of a CSI-RSresource, and/or a periodicity. In an example, a UE may be configured toemploy a same OFDM symbols for downlink CSI-RS 522 and control resourceset (coreset) when the downlink CSI-RS 522 and coreset are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are the outside of PRBs configured for coreset. In anexample, a UE may be configured to employ a same OFDM symbols fordownlink CSI-RS 522 and SS/PBCH blocks when the downlink CSI-RS 522 andSS/PBCH blocks are spatially quasi co-located and resource elementsassociated with the downlink CSI-RS 522 are the outside of PRBsconfigured for SS/PBCH blocks.

In an example, a UE may transmit one or more downlink DM-RSs 523 to abase station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). For example, a radio network may support one or more variableand/or configurable DM-RS patterns for data demodulation. At least onedownlink DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-statisticallyconfigure a UE with a maximum number of front-loaded DM-RS symbols forPDSCH 514. For example, a DM-RS configuration may support one or moreDM-RS ports. For example, for single user-MIMO, a DM-RS configurationmay support at least 8 orthogonal downlink DM-RS ports. For example, formultiuser-MIMO, a DM-RS configuration may support 12 orthogonal downlinkDM-RS ports. A radio network may support, e.g., at least for CP-OFDM, acommon DM-RS structure for DL and UL, wherein a DM-RS location, DM-RSpattern, and/or scrambling sequence may be same or different.

In an example, whether downlink PT-RS 524 is present or not may dependon a RRC configuration. For example, a presence of downlink PT-RS 524may be UE-specifically configured. For example, a presence and/or apattern of downlink PT-RS 524 in a scheduled resource may beUE-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters employed for other purposes(e.g., MCS) which may be indicated by DCI. When configured, a dynamicpresence of downlink PT-RS 524 may be associated with one or more DCIparameters comprising at least MCS. A radio network may supportplurality of PT-RS densities defined in time/frequency domain. Whenpresent, a frequency domain density may be associated with at least oneconfiguration of a scheduled bandwidth. A UE may assume a same precodingfor a DMRS port and a PT-RS port. A number of PT-RS ports may be fewerthan a number of DM-RS ports in a scheduled resource. For example,downlink PT-RS 524 may be confined in the scheduled time/frequencyduration for a UE.

FIG. 6 is a diagram depicting an example transmission time and receptiontime for a carrier as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 32 carriers, in case ofcarrier aggregation, or ranging from 1 to 64 carriers, in case of dualconnectivity. Different radio frame structures may be supported (e.g.,for FDD and for TDD duplex mechanisms). FIG. 6 shows an example frametiming. Downlink and uplink transmissions may be organized into radioframes 601. In this example, radio frame duration is 10 ms. In thisexample, a 10 ms radio frame 601 may be divided into ten equally sizedsubframes 602 with 1 ms duration. Subframe(s) may comprise one or moreslots (e.g. slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6, a subframemay be divided into two equally sized slots 603 with 0.5 ms duration.For example, 10 subframes may be available for downlink transmission and10 subframes may be available for uplink transmissions in a 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. Slot(s) may include a plurality of OFDM symbols 604.The number of OFDM symbols 604 in a slot 605 may depend on the cyclicprefix length. For example, a slot may be 14 OFDM symbols for the samesubcarrier spacing of up to 480 kHz with normal CP. A slot may be 12OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP.A slot may contain downlink, uplink, or a downlink part and an uplinkpart and/or alike.

FIG. 7A is a diagram depicting example sets of OFDM subcarriers as peran aspect of an embodiment of the present disclosure. In the example, agNB may communicate with a wireless device with a carrier with anexample channel bandwidth 700. Arrow(s) in the diagram may depict asubcarrier in a multicarrier OFDM system. The OFDM system may usetechnology such as OFDM technology, SC-FDMA technology, and/or the like.In an example, an arrow 701 shows a subcarrier transmitting informationsymbols. In an example, a subcarrier spacing 702, between two contiguoussubcarriers in a carrier, may be any one of 15 KHz, 30 KHz, 60 KHz, 120KHz, 240 KHz etc. In an example, different subcarrier spacing maycorrespond to different transmission numerologies. In an example, atransmission numerology may comprise at least: a numerology index; avalue of subcarrier spacing; a type of cyclic prefix (CP). In anexample, a gNB may transmit to/receive from a UE on a number ofsubcarriers 703 in a carrier. In an example, a bandwidth occupied by anumber of subcarriers 703 (transmission bandwidth) may be smaller thanthe channel bandwidth 700 of a carrier, due to guard band 704 and 705.In an example, a guard band 704 and 705 may be used to reduceinterference to and from one or more neighbor carriers. A number ofsubcarriers (transmission bandwidth) in a carrier may depend on thechannel bandwidth of the carrier and the subcarrier spacing. Forexample, a transmission bandwidth, for a carrier with 20 MHz channelbandwidth and 15 KHz subcarrier spacing, may be in number of 1024subcarriers.

In an example, a gNB and a wireless device may communicate with multipleCCs when configured with CA. In an example, different component carriersmay have different bandwidth and/or subcarrier spacing, if CA issupported. In an example, a gNB may transmit a first type of service toa UE on a first component carrier. The gNB may transmit a second type ofservice to the UE on a second component carrier. Different type ofservices may have different service requirement (e.g., data rate,latency, reliability), which may be suitable for transmission viadifferent component carrier having different subcarrier spacing and/orbandwidth. FIG. 7B shows an example embodiment. A first componentcarrier may comprise a first number of subcarriers 706 with a firstsubcarrier spacing 709. A second component carrier may comprise a secondnumber of subcarriers 707 with a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 with athird subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. In an example, a carrier mayhave a transmission bandwidth 801. In an example, a resource grid may bein a structure of frequency domain 802 and time domain 803. In anexample, a resource grid may comprise a first number of OFDM symbols ina subframe and a second number of resource blocks, starting from acommon resource block indicated by higher-layer signaling (e.g. RRCsignaling), for a transmission numerology and a carrier. In an example,in a resource grid, a resource unit identified by a subcarrier index anda symbol index may be a resource element 805. In an example, a subframemay comprise a first number of OFDM symbols 807 depending on anumerology associated with a carrier. For example, when a subcarrierspacing of a numerology of a carrier is 15 KHz, a subframe may have 14OFDM symbols for a carrier. When a subcarrier spacing of a numerology is30 KHz, a subframe may have 28 OFDM symbols. When a subcarrier spacingof a numerology is 60 Khz, a subframe may have 56 OFDM symbols, etc. Inan example, a second number of resource blocks comprised in a resourcegrid of a carrier may depend on a bandwidth and a numerology of thecarrier.

As shown in FIG. 8, a resource block 806 may comprise 12 subcarriers. Inan example, multiple resource blocks may be grouped into a ResourceBlock Group (RBG) 804. In an example, a size of a RBG may depend on atleast one of: a RRC message indicating a RBG size configuration; a sizeof a carrier bandwidth; or a size of a bandwidth part of a carrier. Inan example, a carrier may comprise multiple bandwidth parts. A firstbandwidth part of a carrier may have different frequency location and/orbandwidth from a second bandwidth part of the carrier.

In an example, a gNB may transmit a downlink control informationcomprising a downlink or uplink resource block assignment to a wirelessdevice. A base station may transmit to or receive from, a wirelessdevice, data packets (e.g. transport blocks) scheduled and transmittedvia one or more resource blocks and one or more slots according toparameters in a downlink control information and/or RRC message(s). Inan example, a starting symbol relative to a first slot of the one ormore slots may be indicated to the wireless device. In an example, a gNBmay transmit to or receive from, a wireless device, data packetsscheduled on one or more RBGs and one or more slots.

In an example, a gNB may transmit a downlink control informationcomprising a downlink assignment to a wireless device via one or morePDCCHs. The downlink assignment may comprise parameters indicating atleast modulation and coding format; resource allocation; and/or HARQinformation related to DL-SCH. In an example, a resource allocation maycomprise parameters of resource block allocation; and/or slotallocation. In an example, a gNB may dynamically allocate resources to awireless device via a Cell-Radio Network Temporary Identifier (C-RNTI)on one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible allocation when its downlink receptionis enabled. The wireless device may receive one or more downlink datapackage on one or more PDSCH scheduled by the one or more PDCCHs, whensuccessfully detecting the one or more PDCCHs.

In an example, a gNB may allocate Configured Scheduling (CS) resourcesfor down link transmission to a wireless device. The gNB may transmitone or more RRC messages indicating a periodicity of the CS grant. ThegNB may transmit a DCI via a PDCCH addressed to a ConfiguredScheduling-RNTI (CS-RNTI) activating the CS resources. The DCI maycomprise parameters indicating that the downlink grant is a CS grant.The CS grant may be implicitly reused according to the periodicitydefined by the one or more RRC messages, until deactivated.

In an example, a gNB may transmit a downlink control informationcomprising an uplink grant to a wireless device via one or more PDCCHs.The uplink grant may comprise parameters indicating at least modulationand coding format; resource allocation; and/or HARQ information relatedto UL-SCH. In an example, a resource allocation may comprise parametersof resource block allocation; and/or slot allocation. In an example, agNB may dynamically allocate resources to a wireless device via a C-RNTIon one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible resource allocation. The wirelessdevice may transmit one or more uplink data package via one or morePUSCH scheduled by the one or more PDCCHs, when successfully detectingthe one or more PDCCHs.

In an example, a gNB may allocate CS resources for uplink datatransmission to a wireless device. The gNB may transmit one or more RRCmessages indicating a periodicity of the CS grant. The gNB may transmita DCI via a PDCCH addressed to a CS-RNTI activating the CS resources.The DCI may comprise parameters indicating that the uplink grant is a CSgrant. The CS grant may be implicitly reused according to theperiodicity defined by the one or more RRC message, until deactivated.

In an example, a base station may transmit DCI/control signaling viaPDCCH. The DCI may take a format in a plurality of formats. A DCI maycomprise downlink and/or uplink scheduling information (e.g., resourceallocation information, HARQ related parameters, MCS), request for CSI(e.g., aperiodic CQI reports), request for SRS, uplink power controlcommands for one or more cells, one or more timing information (e.g., TBtransmission/reception timing, HARQ feedback timing, etc.), etc. In anexample, a DCI may indicate an uplink grant comprising transmissionparameters for one or more transport blocks. In an example, a DCI mayindicate downlink assignment indicating parameters for receiving one ormore transport blocks. In an example, a DCI may be used by base stationto initiate a contention-free random access at the wireless device. Inan example, the base station may transmit a DCI comprising slot formatindicator (SFI) notifying a slot format. In an example, the base stationmay transmit a DCI comprising pre-emption indication notifying thePRB(s) and/or OFDM symbol(s) where a UE may assume no transmission isintended for the UE. In an example, the base station may transmit a DCIfor group power control of PUCCH or PUSCH or SRS. In an example, a DCImay correspond to an RNTI. In an example, the wireless device may obtainan RNTI in response to completing the initial access (e.g., C-RNTI). Inan example, the base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI). In an example, the wireless device may compute an RNTI(e.g., the wireless device may compute RA-RNTI based on resources usedfor transmission of a preamble). In an example, an RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). In an example, awireless device may monitor a group common search space which may beused by base station for transmitting DCIs that are intended for a groupof UEs. In an example, a group common DCI may correspond to an RNTIwhich is commonly configured for a group of UEs. In an example, awireless device may monitor a UE-specific search space. In an example, aUE specific DCI may correspond to an RNTI configured for the wirelessdevice.

A NR system may support a single beam operation and/or a multi-beamoperation. In a multi-beam operation, a base station may perform adownlink beam sweeping to provide coverage for common control channelsand/or downlink SS blocks, which may comprise at least a PSS, a SSS,and/or PBCH. A wireless device may measure quality of a beam pair linkusing one or more RS s. One or more SS blocks, or one or more CSI-RSresources, associated with a CSI-RS resource index (CRI), or one or moreDM-RSs of PBCH, may be used as RS for measuring quality of a beam pairlink. Quality of a beam pair link may be defined as a reference signalreceived power (RSRP) value, or a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. A RS resource and DM-RSs of a control channel may be calledQCLed when a channel characteristics from a transmission on an RS to awireless device, and that from a transmission on a control channel to awireless device, are similar or same under a configured criterion. In amulti-beam operation, a wireless device may perform an uplink beamsweeping to access a cell.

In an example, a wireless device may be configured to monitor PDCCH onone or more beam pair links simultaneously depending on a capability ofa wireless device. This may increase robustness against beam pair linkblocking. A base station may transmit one or more messages to configurea wireless device to monitor PDCCH on one or more beam pair links indifferent PDCCH OFDM symbols. For example, a base station may transmithigher layer signaling (e.g. RRC signaling) or MAC CE comprisingparameters related to the Rx beam setting of a wireless device formonitoring PDCCH on one or more beam pair links. A base station maytransmit indication of spatial QCL assumption between an DL RS antennaport(s) (for example, cell-specific CSI-RS, or wireless device-specificCSI-RS, or SS block, or PBCH with or without DM-RSs of PBCH), and DL RSantenna port(s) for demodulation of DL control channel. Signaling forbeam indication for a PDCCH may be MAC CE signaling, or RRC signaling,or DCI signaling, or specification-transparent and/or implicit method,and combination of these signaling methods.

For reception of unicast DL data channel, a base station may indicatespatial QCL parameters between DL RS antenna port(s) and DM-RS antennaport(s) of DL data channel. The base station may transmit DCI (e.g.downlink grants) comprising information indicating the RS antennaport(s). The information may indicate RS antenna port(s) which may beQCLed with the DM-RS antenna port(s). Different set of DM-RS antennaport(s) for a DL data channel may be indicated as QCL with different setof the RS antenna port(s).

FIG. 9A is an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. For example, in a multi-beamoperation, a base station 120 may transmit SS blocks in multiple beams,together forming a SS burst 940. One or more SS blocks may betransmitted on one beam. If multiple SS bursts 940 are transmitted withmultiple beams, SS bursts together may form SS burst set 950.

A wireless device may further use CSI-RS in the multi-beam operation forestimating a beam quality of a links between a wireless device and abase station. A beam may be associated with a CSI-RS. For example, awireless device may, based on a RSRP measurement on CSI-RS, report abeam index, as indicated in a CRI for downlink beam selection, andassociated with a RSRP value of a beam. A CSI-RS may be transmitted on aCSI-RS resource including at least one of one or more antenna ports, oneor more time or frequency radio resources. A CSI-RS resource may beconfigured in a cell-specific way by common RRC signaling, or in awireless device-specific way by dedicated RRC signaling, and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be transmitted periodically, or using aperiodictransmission, or using a multi-shot or semi-persistent transmission. Forexample, in a periodic transmission in FIG. 9A, a base station 120 maytransmit configured CSI-RS resources 940 periodically using a configuredperiodicity in a time domain. In an aperiodic transmission, a configuredCSI-RS resource may be transmitted in a dedicated time slot. In amulti-shot or semi-persistent transmission, a configured CSI-RS resourcemay be transmitted within a configured period. Beams used for CSI-RStransmission may have different beam width than beams used for SS-blockstransmission.

FIG. 9B is an example of a beam management procedure in an example newradio network. A base station 120 and/or a wireless device 110 mayperform a downlink L1/L2 beam management procedure. One or more of thefollowing downlink L1/L2 beam management procedures may be performedwithin one or more wireless devices 110 and one or more base stations120. In an example, a P-1 procedure 910 may be used to enable thewireless device 110 to measure one or more Transmission (Tx) beamsassociated with the base station 120 to support a selection of a firstset of Tx beams associated with the base station 120 and a first set ofRx beam(s) associated with a wireless device 110. For beamforming at abase station 120, a base station 120 may sweep a set of different TXbeams. For beamforming at a wireless device 110, a wireless device 110may sweep a set of different Rx beams. In an example, a P-2 procedure920 may be used to enable a wireless device 110 to measure one or moreTx beams associated with a base station 120 to possibly change a firstset of Tx beams associated with a base station 120. A P-2 procedure 920may be performed on a possibly smaller set of beams for beam refinementthan in the P-1 procedure 910. A P-2 procedure 920 may be a special caseof a P-1 procedure 910. In an example, a P-3 procedure 930 may be usedto enable a wireless device 110 to measure at least one Tx beamassociated with a base station 120 to change a first set of Rx beamsassociated with a wireless device 110.

A wireless device 110 may transmit one or more beam management reportsto a base station 120. In one or more beam management reports, awireless device 110 may indicate some beam pair quality parameters,comprising at least, one or more beam identifications; RSRP; PrecodingMatrix Indicator (PMI)/Channel Quality Indicator (CQI)/Rank Indicator(RI) of a subset of configured beams. Based on one or more beammanagement reports, a base station 120 may transmit to a wireless device110 a signal indicating that one or more beam pair links are one or moreserving beams. A base station 120 may transmit PDCCH and PDSCH for awireless device 110 using one or more serving beams.

In an example embodiment, new radio network may support a BandwidthAdaptation (BA). In an example, receive and/or transmit bandwidthsconfigured by an UE employing a BA may not be large. For example, areceive and/or transmit bandwidths may not be as large as a bandwidth ofa cell. Receive and/or transmit bandwidths may be adjustable. Forexample, a UE may change receive and/or transmit bandwidths, e.g., toshrink during period of low activity to save power. For example, a UEmay change a location of receive and/or transmit bandwidths in afrequency domain, e.g. to increase scheduling flexibility. For example,a UE may change a subcarrier spacing, e.g. to allow different services.

In an example embodiment, a subset of a total cell bandwidth of a cellmay be referred to as a Bandwidth Part (BWP). A base station mayconfigure a UE with one or more BWPs to achieve a BA. For example, abase station may indicate, to a UE, which of the one or more(configured) BWPs is an active BWP.

FIG. 10 is an example diagram of 3 BWPs configured: BWP1 (1010 and 1050)with a width of 40 MHz and subcarrier spacing of 15 kHz; BWP2 (1020 and1040) with a width of 10 MHz and subcarrier spacing of 15 kHz; BWP3 1030with a width of 20 MHz and subcarrier spacing of 60 kHz.

In an example, a UE, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g. RRC layer)for a cell a set of one or more BWPs (e.g., at most four BWPs) forreceptions by the UE (DL BWP set) in a DL bandwidth by at least oneparameter DL-BWP and a set of one or more BWPs (e.g., at most four BWPs)for transmissions by a UE (UL BWP set) in an UL bandwidth by at leastone parameter UL-BWP for a cell.

To enable BA on the PCell, a base station may configure a UE with one ormore UL and DL BWP pairs. To enable BA on SCells (e.g., in case of CA),a base station may configure a UE at least with one or more DL BWPs(e.g., there may be none in an UL).

In an example, an initial active DL BWP may be defined by at least oneof a location and number of contiguous PRBs, a subcarrier spacing, or acyclic prefix, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a UE is configured with a secondary carrier on a primary cell, the UEmay be configured with an initial BWP for random access procedure on asecondary carrier.

In an example, for unpaired spectrum operation, a UE may expect that acenter frequency for a DL BWP may be same as a center frequency for a ULBWP.

For example, for a DL BWP or an UL BWP in a set of one or more DL BWPsor one or more UL BWPs, respectively, a base station maysemi-statistically configure a UE for a cell with one or more parametersindicating at least one of following: a subcarrier spacing; a cyclicprefix; a number of contiguous PRBs; an index in the set of one or moreDL BWPs and/or one or more UL BWPs; a link between a DL BWP and an ULBWP from a set of configured DL BWPs and UL BWPs; a DCI detection to aPDSCH reception timing; a PDSCH reception to a HARQ-ACK transmissiontiming value; a DCI detection to a PUSCH transmission timing value; anoffset of a first PRB of a DL bandwidth or an UL bandwidth,respectively, relative to a first PRB of a bandwidth.

In an example, for a DL BWP in a set of one or more DL BWPs on a PCell,a base station may configure a UE with one or more control resource setsfor at least one type of common search space and/or one UE-specificsearch space. For example, a base station may not configure a UE withouta common search space on a PCell, or on a PSCell, in an active DL BWP.

For an UL BWP in a set of one or more UL BWPs, a base station mayconfigure a UE with one or more resource sets for one or more PUCCHtransmissions.

In an example, if a DCI comprises a BWP indicator field, a BWP indicatorfield value may indicate an active DL BWP, from a configured DL BWP set,for one or more DL receptions. If a DCI comprises a BWP indicator field,a BWP indicator field value may indicate an active UL BWP, from aconfigured UL BWP set, for one or more UL transmissions.

In an example, for a PCell, a base station may semi-statisticallyconfigure a UE with a default DL BWP among configured DL BWPs. If a UEis not provided a default DL BWP, a default BWP may be an initial activeDL BWP.

In an example, a base station may configure a UE with a timer value fora PCell. For example, a UE may start a timer, referred to as BWPinactivity timer, when a UE detects a DCI indicating an active DL BWP,other than a default DL BWP, for a paired spectrum operation or when aUE detects a DCI indicating an active DL BWP or UL BWP, other than adefault DL BWP or UL BWP, for an unpaired spectrum operation. The UE mayincrement the timer by an interval of a first value (e.g., the firstvalue may be 1 millisecond or 0.5 milliseconds) if the UE does notdetect a DCI during the interval for a paired spectrum operation or foran unpaired spectrum operation. In an example, the timer may expire whenthe timer is equal to the timer value. A UE may switch to the default DLBWP from an active DL BWP when the timer expires.

In an example, a base station may semi-statistically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of BWP inactivity timer(for example, the second BWP may be a default BWP). For example, FIG. 10is an example diagram of 3 BWPs configured, BWP1 (1010 and 1050), BWP2(1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be a defaultBWP. BWP1 (1010) may be an initial active BWP. In an example, a UE mayswitch an active BWP from BWP1 1010 to BWP2 1020 in response to anexpiry of BWP inactivity timer. For example, a UE may switch an activeBWP from BWP2 1020 to BWP3 1030 in response to receiving a DCIindicating BWP3 1030 as an active BWP. Switching an active BWP from BWP31030 to BWP2 1040 and/or from BWP2 1040 to BWP1 1050 may be in responseto receiving a DCI indicating an active BWP and/or in response to anexpiry of BWP inactivity timer.

In an example, if a UE is configured for a secondary cell with a defaultDL BWP among configured DL BWPs and a timer value, UE procedures on asecondary cell may be same as on a primary cell using the timer valuefor the secondary cell and the default DL BWP for the secondary cell.

In an example, if a base station configures a UE with a first active DLBWP and a first active UL BWP on a secondary cell or carrier, a UE mayemploy an indicated DL BWP and an indicated UL BWP on a secondary cellas a respective first active DL BWP and first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows employing a multi connectivity(e.g. dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A is an example diagram of a protocol structure of awireless device 110 (e.g. UE) with CA and/or multi connectivity as peran aspect of an embodiment. FIG. 11B is an example diagram of a protocolstructure of multiple base stations with CA and/or multi connectivity asper an aspect of an embodiment. The multiple base stations may comprisea master node, MN 1130 (e.g. a master node, a master base station, amaster gNB, a master eNB, and/or the like) and a secondary node, SN 1150(e.g. a secondary node, a secondary base station, a secondary gNB, asecondary eNB, and/or the like). A master node 1130 and a secondary node1150 may co-work to communicate with a wireless device 110.

When multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception/transmissionfunctions in an RRC connected state, may be configured to utilize radioresources provided by multiple schedulers of a multiple base stations.Multiple base stations may be inter-connected via a non-ideal or idealbackhaul (e.g. Xn interface, X2 interface, and/or the like). A basestation involved in multi connectivity for a certain wireless device mayperform at least one of two different roles: a base station may eitheract as a master base station or as a secondary base station. In multiconnectivity, a wireless device may be connected to one master basestation and one or more secondary base stations. In an example, a masterbase station (e.g. the MN 1130) may provide a master cell group (MCG)comprising a primary cell and/or one or more secondary cells for awireless device (e.g. the wireless device 110). A secondary base station(e.g. the SN 1150) may provide a secondary cell group (SCG) comprising aprimary secondary cell (PSCell) and/or one or more secondary cells for awireless device (e.g. the wireless device 110).

In multi connectivity, a radio protocol architecture that a beareremploys may depend on how a bearer is setup. In an example, threedifferent type of bearer setup options may be supported: an MCG bearer,an SCG bearer, and/or a split bearer. A wireless device mayreceive/transmit packets of an MCG bearer via one or more cells of theMCG, and/or may receive/transmits packets of an SCG bearer via one ormore cells of an SCG. Multi-connectivity may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not beconfigured/implemented in some of the example embodiments.

In an example, a wireless device (e.g. Wireless Device 110) may transmitand/or receive: packets of an MCG bearer via an SDAP layer (e.g. SDAP1110), a PDCP layer (e.g. NR PDCP 1111), an RLC layer (e.g. MN RLC1114), and a MAC layer (e.g. MN MAC 1118); packets of a split bearer viaan SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1112), one ofa master or secondary RLC layer (e.g. MN RLC 1115, SN RLC 1116), and oneof a master or secondary MAC layer (e.g. MN MAC 1118, SN MAC 1119);and/or packets of an SCG bearer via an SDAP layer (e.g. SDAP 1110), aPDCP layer (e.g. NR PDCP 1113), an RLC layer (e.g. SN RLC 1117), and aMAC layer (e.g. MN MAC 1119).

In an example, a master base station (e.g. MN 1130) and/or a secondarybase station (e.g. SN 1150) may transmit/receive: packets of an MCGbearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g. NR PDCP 1121, NR PDCP1142), a master node RLC layer (e.g. MN RLC 1124, MN RLC 1125), and amaster node MAC layer (e.g. MN MAC 1128); packets of an SCG bearer via amaster or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1122, NR PDCP 1143), asecondary node RLC layer (e.g. SN RLC 1146, SN RLC 1147), and asecondary node MAC layer (e.g. SN MAC 1148); packets of a split bearervia a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1123, NR PDCP 1141), amaster or secondary node RLC layer (e.g. MN RLC 1126, SN RLC 1144, SNRLC 1145, MN RLC 1127), and a master or secondary node MAC layer (e.g.MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities: one MAC entity (e.g. MN MAC 1118) for a master base station,and other MAC entities (e.g. SN MAC 1119) for a secondary base station.In multi-connectivity, a configured set of serving cells for a wirelessdevice may comprise two subsets: an MCG comprising serving cells of amaster base station, and SCGs comprising serving cells of a secondarybase station. For an SCG, one or more of following configurations may beapplied: at least one cell of an SCG has a configured UL CC and at leastone cell of a SCG, named as primary secondary cell (PSCell, PCell ofSCG, or sometimes called PCell), is configured with PUCCH resources;when an SCG is configured, there may be at least one SCG bearer or oneSplit bearer; upon detection of a physical layer problem or a randomaccess problem on a PSCell, or a number of NR RLC retransmissions hasbeen reached associated with the SCG, or upon detection of an accessproblem on a PSCell during a SCG addition or a SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, forsplit bearer, a DL data transfer over a master base station may bemaintained; an NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer; PCell and/or PSCell may not be de-activated; PSCellmay be changed with a SCG change procedure (e.g. with security keychange and a RACH procedure); and/or a bearer type change between asplit bearer and a SCG bearer or simultaneous configuration of a SCG anda split bearer may or may not supported.

With respect to interaction between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be applied: a master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice; a master base station may (e.g. based on received measurementreports, traffic conditions, and/or bearer types) may decide to requesta secondary base station to provide additional resources (e.g. servingcells) for a wireless device; upon receiving a request from a masterbase station, a secondary base station may create/modify a containerthat may result in configuration of additional serving cells for awireless device (or decide that the secondary base station has noresource available to do so); for a UE capability coordination, a masterbase station may provide (a part of) an AS configuration and UEcapabilities to a secondary base station; a master base station and asecondary base station may exchange information about a UE configurationby employing of RRC containers (inter-node messages) carried via Xnmessages; a secondary base station may initiate a reconfiguration of thesecondary base station existing serving cells (e.g. PUCCH towards thesecondary base station); a secondary base station may decide which cellis a PSCell within a SCG; a master base station may or may not changecontent of RRC configurations provided by a secondary base station; incase of a SCG addition and/or a SCG SCell addition, a master basestation may provide recent (or the latest) measurement results for SCGcell(s); a master base station and secondary base stations may receiveinformation of SFN and/or subframe offset of each other from OAM and/orvia an Xn interface, (e.g. for a purpose of DRX alignment and/oridentification of a measurement gap). In an example, when adding a newSCG SCell, dedicated RRC signaling may be used for sending requiredsystem information of a cell as for CA, except for a SFN acquired from aMIB of a PSCell of a SCG.

FIG. 12 is an example diagram of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival during RRC_CONNECTED when UL synchronization status isnon-synchronized, transition from RRC_Inactive, and/or request for othersystem information. For example, a PDCCH order, a MAC entity, and/or abeam failure indication may initiate a random access procedure.

In an example embodiment, a random access procedure may be at least oneof a contention based random access procedure and a contention freerandom access procedure. For example, a contention based random accessprocedure may comprise, one or more Msg 1 1220 transmissions, one ormore Msg2 1230 transmissions, one or more Msg3 1240 transmissions, andcontention resolution 1250. For example, a contention free random accessprocedure may comprise one or more Msg 1 1220 transmissions and one ormore Msg2 1230 transmissions.

In an example, a base station may transmit (e.g., unicast, multicast, orbroadcast), to a UE, a RACH configuration 1210 via one or more beams.The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: available set of PRACH resourcesfor a transmission of a random access preamble, initial preamble power(e.g., random access preamble initial received target power), an RSRPthreshold for a selection of a SS block and corresponding PRACHresource, a power-ramping factor (e.g., random access preamble powerramping step), random access preamble index, a maximum number ofpreamble transmission, preamble group A and group B, a threshold (e.g.,message size) to determine the groups of random access preambles, a setof one or more random access preambles for system information requestand corresponding PRACH resource(s), if any, a set of one or more randomaccess preambles for beam failure recovery request and correspondingPRACH resource(s), if any, a time window to monitor RA response(s), atime window to monitor response(s) on beam failure recovery request,and/or a contention resolution timer.

In an example, the Msg1 1220 may be one or more transmissions of arandom access preamble. For a contention based random access procedure,a UE may select a SS block with a RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a UE may select one or morerandom access preambles from a group A or a group B depending on apotential Msg3 1240 size. If a random access preambles group B does notexist, a UE may select the one or more random access preambles from agroup A. A UE may select a random access preamble index randomly (e.g.with equal probability or a normal distribution) from one or more randomaccess preambles associated with a selected group. If a base stationsemi-statistically configures a UE with an association between randomaccess preambles and SS blocks, the UE may select a random accesspreamble index randomly with equal probability from one or more randomaccess preambles associated with a selected SS block and a selectedgroup.

For example, a UE may initiate a contention free random access procedurebased on a beam failure indication from a lower layer. For example, abase station may semi-statistically configure a UE with one or morecontention free PRACH resources for beam failure recovery requestassociated with at least one of SS blocks and/or CSI-RS s. If at leastone of SS blocks with a RSRP above a first RSRP threshold amongstassociated SS blocks or at least one of CSI-RSs with a RSRP above asecond RSRP threshold amongst associated CSI-RSs is available, a UE mayselect a random access preamble index corresponding to a selected SSblock or CSI-RS from a set of one or more random access preambles forbeam failure recovery request.

For example, a UE may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. If a base station does not configure a UE with at least onecontention free PRACH resource associated with SS blocks or CSI-RS, theUE may select a random access preamble index. If a base stationconfigures a UE with one or more contention free PRACH resourcesassociated with SS blocks and at least one SS block with a RSRP above afirst RSRP threshold amongst associated SS blocks is available, the UEmay select the at least one SS block and select a random access preamblecorresponding to the at least one SS block. If a base station configuresa UE with one or more contention free PRACH resources associated withCSI-RSs and at least one CSI-RS with a RSRP above a second RSPRthreshold amongst the associated CSI-RSs is available, the UE may selectthe at least one CSI-RS and select a random access preamblecorresponding to the at least one CSI-RS.

A UE may perform one or more Msg1 1220 transmissions by transmitting theselected random access preamble. For example, if a UE selects an SSblock and is configured with an association between one or more PRACHoccasions and one or more SS blocks, the UE may determine an PRACHoccasion from one or more PRACH occasions corresponding to a selected SSblock. For example, if a UE selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs, the UE may determine a PRACH occasion from one or more PRACHoccasions corresponding to a selected CSI-RS. A UE may transmit, to abase station, a selected random access preamble via a selected PRACHoccasions. A UE may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. A UE may determine a RA-RNTIassociated with a selected PRACH occasions in which a selected randomaccess preamble is transmitted. For example, a UE may not determine aRA-RNTI for a beam failure recovery request. A UE may determine anRA-RNTI at least based on an index of a first OFDM symbol and an indexof a first slot of a selected PRACH occasions, and/or an uplink carrierindex for a transmission of Msg1 1220.

In an example, a UE may receive, from a base station, a random accessresponse, Msg 2 1230. A UE may start a time window (e.g., ra-ResponseWindow) to monitor a random access response. For beam failure recoveryrequest, a base station may configure a UE with a different time window(e.g., bfr-Response Window) to monitor response on beam failure recoveryrequest. For example, a UE may start a time window (e.g.,ra-ResponseWindow or bfr-Response Window) at a start of a first PDCCHoccasion after a fixed duration of one or more symbols from an end of apreamble transmission. If a UE transmits multiple preambles, the UE maystart a time window at a start of a first PDCCH occasion after a fixedduration of one or more symbols from an end of a first preambletransmission. A UE may monitor a PDCCH of a cell for at least one randomaccess response identified by a RA-RNTI or for at least one response tobeam failure recovery request identified by a C-RNTI while a timer for atime window is running.

In an example, a UE may consider a reception of random access responsesuccessful if at least one random access response comprises a randomaccess preamble identifier corresponding to a random access preambletransmitted by the UE. A UE may consider the contention free randomaccess procedure successfully completed if a reception of random accessresponse is successful. If a contention free random access procedure istriggered for a beam failure recovery request, a UE may consider acontention free random access procedure successfully complete if a PDCCHtransmission is addressed to a C-RNTI. In an example, if at least onerandom access response comprises a random access preamble identifier, aUE may consider the random access procedure successfully completed andmay indicate a reception of an acknowledgement for a system informationrequest to upper layers. If a UE has signaled multiple preambletransmissions, the UE may stop transmitting remaining preambles (if any)in response to a successful reception of a corresponding random accessresponse.

In an example, a UE may perform one or more Msg 3 1240 transmissions inresponse to a successful reception of random access response (e.g., fora contention based random access procedure). A UE may adjust an uplinktransmission timing based on a timing advanced command indicated by arandom access response and may transmit one or more transport blocksbased on an uplink grant indicated by a random access response.Subcarrier spacing for PUSCH transmission for Msg3 1240 may be providedby at least one higher layer (e.g. RRC) parameter. A UE may transmit arandom access preamble via PRACH and Msg3 1240 via PUSCH on a same cell.A base station may indicate an UL BWP for a PUSCH transmission of Msg31240 via system information block. A UE may employ HARQ for aretransmission of Msg 3 1240.

In an example, multiple UEs may perform Msg 1 1220 by transmitting asame preamble to a base station and receive, from the base station, asame random access response comprising an identity (e.g., TC-RNTI).Contention resolution 1250 may ensure that a UE does not incorrectly usean identity of another UE. For example, contention resolution 1250 maybe based on C-RNTI on PDCCH or a UE contention resolution identity onDL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UEmay perform contention resolution 1250 based on a reception of a PDCCHtransmission that is addressed to the C-RNTI. In response to detectionof a C-RNTI on a PDCCH, a UE may consider contention resolution 1250successful and may consider a random access procedure successfullycompleted. If a UE has no valid C-RNTI, a contention resolution may beaddressed by employing a TC-RNTI. For example, if a MAC PDU issuccessfully decoded and a MAC PDU comprises a UE contention resolutionidentity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, a UEmay consider the contention resolution 1250 successful and may considerthe random access procedure successfully completed.

FIG. 13 is an example structure for MAC entities as per an aspect of anembodiment. In an example, a wireless device may be configured tooperate in a multi-connectivity mode. A wireless device in RRC_CONNECTEDwith multiple RX/TX may be configured to utilize radio resourcesprovided by multiple schedulers located in a plurality of base stations.The plurality of base stations may be connected via a non-ideal or idealbackhaul over the Xn interface. In an example, a base station in aplurality of base stations may act as a master base station or as asecondary base station. A wireless device may be connected to one masterbase station and one or more secondary base stations. A wireless devicemay be configured with multiple MAC entities, e.g. one MAC entity formaster base station, and one or more other MAC entities for secondarybase station(s). In an example, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 illustrates an examplestructure for MAC entities when MCG and SCG are configured for awireless device.

In an example, at least one cell in a SCG may have a configured UL CC,wherein a cell of at least one cell may be called PSCell or PCell ofSCG, or sometimes may be simply called PCell. A PSCell may be configuredwith PUCCH resources. In an example, when a SCG is configured, there maybe at least one SCG bearer or one split bearer. In an example, upondetection of a physical layer problem or a random access problem on aPSCell, or upon reaching a number of RLC retransmissions associated withthe SCG, or upon detection of an access problem on a PSCell during a SCGaddition or a SCG change: an RRC connection re-establishment proceduremay not be triggered, UL transmissions towards cells of an SCG may bestopped, a master base station may be informed by a UE of a SCG failuretype and DL data transfer over a master base station may be maintained.

In an example, a MAC sublayer may provide services such as data transferand radio resource allocation to upper layers (e.g. 1310 or 1320). A MACsublayer may comprise a plurality of MAC entities (e.g. 1350 and 1360).A MAC sublayer may provide data transfer services on logical channels.To accommodate different kinds of data transfer services, multiple typesof logical channels may be defined. A logical channel may supporttransfer of a particular type of information. A logical channel type maybe defined by what type of information (e.g., control or data) istransferred. For example, BCCH, PCCH, CCCH and DCCH may be controlchannels and DTCH may be a traffic channel. In an example, a first MACentity (e.g. 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCHand MAC control elements. In an example, a second MAC entity (e.g. 1320)may provide services on BCCH, DCCH, DTCH and MAC control elements.

A MAC sublayer may expect from a physical layer (e.g. 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,signaling of scheduling request or measurements (e.g. CQI). In anexample, in dual connectivity, two MAC entities may be configured for awireless device: one for MCG and one for SCG. A MAC entity of wirelessdevice may handle a plurality of transport channels. In an example, afirst MAC entity may handle first transport channels comprising a PCCHof MCG, a first BCH of MCG, one or more first DL-SCHs of MCG, one ormore first UL-SCHs of MCG and one or more first RACHs of MCG. In anexample, a second MAC entity may handle second transport channelscomprising a second BCH of SCG, one or more second DL-SCHs of SCG, oneor more second UL-SCHs of SCG and one or more second RACHs of SCG.

In an example, if a MAC entity is configured with one or more SCells,there may be multiple DL-SCHs and there may be multiple UL-SCHs as wellas multiple RACHs per MAC entity. In an example, there may be one DL-SCHand UL-SCH on a SpCell. In an example, there may be one DL-SCH, zero orone UL-SCH and zero or one RACH for an SCell. A DL-SCH may supportreceptions using different numerologies and/or TTI duration within a MACentity. A UL-SCH may also support transmissions using differentnumerologies and/or TTI duration within the MAC entity.

In an example, a MAC sublayer may support different functions and maycontrol these functions with a control (e.g. 1355 or 1365) element.Functions performed by a MAC entity may comprise mapping between logicalchannels and transport channels (e.g., in uplink or downlink),multiplexing (e.g. 1352 or 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TB) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g. 1352 or 1362) of MAC SDUs to one or different logical channelsfrom transport blocks (TB) delivered from the physical layer ontransport channels (e.g., in downlink), scheduling information reporting(e.g., in uplink), error correction through HARQ in uplink or downlink(e.g. 1363), and logical channel prioritization in uplink (e.g. 1351 or1361). A MAC entity may handle a random access process (e.g. 1354 or1364).

FIG. 14 is an example diagram of a RAN architecture comprising one ormore base stations. In an example, a protocol stack (e.g. RRC, SDAP,PDCP, RLC, MAC, and PHY) may be supported at a node. A base station(e.g. gNB 120A or 120B) may comprise a base station central unit (CU)(e.g. gNB-CU 1420A or 1420B) and at least one base station distributedunit (DU) (e.g. gNB-DU 1430A, 1430B, 1430C, or 1430D) if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g. CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. In an example, an Xn interface may be configuredbetween base station CUs.

In an example, a base station CU may comprise an RRC function, an SDAPlayer, and a PDCP layer, and base station DUs may comprise an RLC layer,a MAC layer, and a PHY layer. In an example, various functional splitoptions between a base station CU and base station DUs may be possibleby locating different combinations of upper protocol layers (RANfunctions) in a base station CU and different combinations of lowerprotocol layers (RAN functions) in base station DUs. A functional splitmay support flexibility to move protocol layers between a base stationCU and base station DUs depending on service requirements and/or networkenvironments.

In an example, functional split options may be configured per basestation, per base station CU, per base station DU, per UE, per bearer,per slice, or with other granularities. In per base station CU split, abase station CU may have a fixed split option, and base station DUs maybe configured to match a split option of a base station CU. In per basestation DU split, a base station DU may be configured with a differentsplit option, and a base station CU may provide different split optionsfor different base station DUs. In per UE split, a base station (basestation CU and at least one base station DUs) may provide differentsplit options for different wireless devices. In per bearer split,different split options may be utilized for different bearers. In perslice splice, different split options may be applied for differentslices.

FIG. 15 is an example diagram showing RRC state transitions of awireless device. In an example, a wireless device may be in at least oneRRC state among an RRC connected state (e.g. RRC_Connected 1530,RRC_Connected), an RRC idle state (e.g. RRC_Idle 1510, RRC_Idle), and/oran RRC inactive state (e.g. RRC_Inactive 1520, RRC_Inactive). In anexample, in an RRC connected state, a wireless device may have at leastone RRC connection with at least one base station (e.g. gNB and/or eNB),which may have a UE context of the wireless device. A UE context (e.g. awireless device context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an example, in an RRC idle state, a wireless device may nothave an RRC connection with a base station, and a UE context of awireless device may not be stored in a base station. In an example, inan RRC inactive state, a wireless device may not have an RRC connectionwith a base station. A UE context of a wireless device may be stored ina base station, which may be called as an anchor base station (e.g. lastserving base station).

In an example, a wireless device may transition a UE RRC state betweenan RRC idle state and an RRC connected state in both ways (e.g.connection release 1540 or connection establishment 1550; or connectionreestablishment) and/or between an RRC inactive state and an RRCconnected state in both ways (e.g. connection inactivation 1570 orconnection resume 1580). In an example, a wireless device may transitionits RRC state from an RRC inactive state to an RRC idle state (e.g.connection release 1560).

In an example, an anchor base station may be a base station that maykeep a UE context (a wireless device context) of a wireless device atleast during a time period that a wireless device stays in a RANnotification area (RNA) of an anchor base station, and/or that awireless device stays in an RRC inactive state. In an example, an anchorbase station may be a base station that a wireless device in an RRCinactive state was lastly connected to in a latest RRC connected stateor that a wireless device lastly performed an RNA update procedure in.In an example, an RNA may comprise one or more cells operated by one ormore base stations. In an example, a base station may belong to one ormore RNAs. In an example, a cell may belong to one or more RNAs.

In an example, a wireless device may transition a UE RRC state from anRRC connected state to an RRC inactive state in a base station. Awireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

In an example, an anchor base station may broadcast a message (e.g. RANpaging message) to base stations of an RNA to reach to a wireless devicein an RRC inactive state, and/or the base stations receiving the messagefrom the anchor base station may broadcast and/or multicast anothermessage (e.g. paging message) to wireless devices in their coveragearea, cell coverage area, and/or beam coverage area associated with theRNA through an air interface.

In an example, when a wireless device in an RRC inactive state movesinto a new RNA, the wireless device may perform an RNA update (RNAU)procedure, which may comprise a random access procedure by the wirelessdevice and/or a UE context retrieve procedure. A UE context retrieve maycomprise: receiving, by a base station from a wireless device, a randomaccess preamble; and fetching, by a base station, a UE context of thewireless device from an old anchor base station. Fetching may comprise:sending a retrieve UE context request message comprising a resumeidentifier to the old anchor base station and receiving a retrieve UEcontext response message comprising the UE context of the wirelessdevice from the old anchor base station.

In an example embodiment, a wireless device in an RRC inactive state mayselect a cell to camp on based on at least a on measurement results forone or more cells, a cell where a wireless device may monitor an RNApaging message and/or a core network paging message from a base station.In an example, a wireless device in an RRC inactive state may select acell to perform a random access procedure to resume an RRC connectionand/or to transmit one or more packets to a base station (e.g. to anetwork). In an example, if a cell selected belongs to a different RNAfrom an RNA for a wireless device in an RRC inactive state, the wirelessdevice may initiate a random access procedure to perform an RNA updateprocedure. In an example, if a wireless device in an RRC inactive statehas one or more packets, in a buffer, to transmit to a network, thewireless device may initiate a random access procedure to transmit oneor more packets to a base station of a cell that the wireless deviceselects. A random access procedure may be performed with two messages(e.g. 2 stage random access) and/or four messages (e.g. 4 stage randomaccess) between the wireless device and the base station.

In an example embodiment, a base station receiving one or more uplinkpackets from a wireless device in an RRC inactive state may fetch a UEcontext of a wireless device by transmitting a retrieve UE contextrequest message for the wireless device to an anchor base station of thewireless device based on at least one of an AS context identifier, anRNA identifier, a base station identifier, a resume identifier, and/or acell identifier received from the wireless device. In response tofetching a UE context, a base station may transmit a path switch requestfor a wireless device to a core network entity (e.g. AMF, MME, and/orthe like). A core network entity may update a downlink tunnel endpointidentifier for one or more bearers established for the wireless devicebetween a user plane core network entity (e.g. UPF, S-GW, and/or thelike) and a RAN node (e.g. the base station), e.g. changing a downlinktunnel endpoint identifier from an address of the anchor base station toan address of the base station.

A gNB may communicate with a wireless device via a wireless networkemploying one or more new radio technologies. The one or more radiotechnologies may comprise at least one of: multiple technologies relatedto physical layer; multiple technologies related to medium accesscontrol layer; and/or multiple technologies related to radio resourcecontrol layer. Example embodiments of enhancing the one or more radiotechnologies may improve performance of a wireless network. Exampleembodiments may increase the system throughput, or data rate oftransmission. Example embodiments may reduce battery consumption of awireless device. Example embodiments may improve latency of datatransmission between a gNB and a wireless device. Example embodimentsmay improve network coverage of a wireless network. Example embodimentsmay improve transmission efficiency of a wireless network.

Example Downlink Control Information (DCI)

In an example, a gNB may transmit a DCI via a PDCCH for at least one of:scheduling assignment/grant; slot format notification; pre-emptionindication; and/or power-control commends. More specifically, the DCImay comprise at least one of: identifier of a DCI format; downlinkscheduling assignment(s); uplink scheduling grant(s); slot formatindicator; pre-emption indication; power-control for PUCCH/PUSCH; and/orpower-control for SRS.

In an example, a downlink scheduling assignment DCI may compriseparameters indicating at least one of: identifier of a DCI format; PDSCHresource indication; transport format; HARQ information; controlinformation related to multiple antenna schemes; and/or a command forpower control of the PUCCH.

In an example, an uplink scheduling grant DCI may comprise parametersindicating at least one of: identifier of a DCI format; PUSCH resourceindication; transport format; HARQ related information; and/or a powercontrol command of the PUSCH.

In an example, different types of control information may correspond todifferent DCI message sizes. For example, supporting multiple beamsand/or spatial multiplexing in the spatial domain and noncontiguousallocation of RBs in the frequency domain may require a largerscheduling message, in comparison with an uplink grant allowing forfrequency-contiguous allocation. DCI may be categorized into differentDCI formats, where a format corresponds to a certain message size and/orusage.

In an example, a wireless device may monitor one or more PDCCH fordetecting one or more DCI with one or more DCI format, in common searchspace or wireless device-specific search space. In an example, awireless device may monitor PDCCH with a limited set of DCI format, tosave power consumption. The more DCI format to be detected, the morepower be consumed at the wireless device.

In an example, the information in the DCI formats for downlinkscheduling may comprise at least one of: identifier of a DCI format;carrier indicator; frequency domain resource assignment; time domainresource assignment; bandwidth part indicator; HARQ process number; oneor more MCS; one or more NDI; one or more RV; MIMO related information;Downlink assignment index (DAI); PUCCH resource indicator;PDSCH-to-HARQ_feedback timing indicator; TPC for PUCCH; SRS request; andpadding if necessary. In an example, the MIMO related information maycomprise at least one of: PMI; precoding information; transport blockswap flag; power offset between PDSCH and reference signal;reference-signal scrambling sequence; number of layers; and/or antennaports for the transmission; and/or Transmission Configuration Indication(TCI).

In an example, the information in the DCI formats used for uplinkscheduling may comprise at least one of: an identifier of a DCI format;carrier indicator; bandwidth part indication; resource allocation type;frequency domain resource assignment; time domain resource assignment;MCS; NDI; Phase rotation of the uplink DMRS; precoding information; CSIrequest; SRS request; Uplink index/DAI; TPC for PUSCH; and/or padding ifnecessary.

In an example, a gNB may perform CRC scrambling for a DCI, beforetransmitting the DCI via a PDCCH. The gNB may perform CRC scrambling bybinary addition of multiple bits of at least one wireless deviceidentifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI,TPC-PUSCH-RNTI, SP CSI C-RNTI, or TPC-SRS-RNTI) and the CRC bits of theDCI. The wireless device may check the CRC bits of the DCI, whendetecting the DCI. The wireless device may receive the DCI when the CRCis scrambled by a sequence of bits that is the same as the at least onewireless device identifier.

In an example, in order to support wide bandwidth operation, a gNB maytransmit one or more PDCCH in different control resource sets(coresets). A gNB may transmit one or more RRC message comprisingconfiguration parameters of one or more coresets. A coreset may compriseat least one of: a first OFDM symbol; a number of consecutive OFDMsymbols; a set of resource blocks; a CCE-to-REG mapping. In an example,a gNB may transmit a PDCCH in a dedicated coreset for particularpurpose, for example, for beam failure recovery confirmation.

In an example, a wireless device may monitor PDCCH for detecting DCI inone or more configured coresets, to reduce the power consumption.

Example MAC PDU Structure.

A gNB may transmit one or more MAC PDU to a wireless device. In anexample, a MAC PDU may be a bit string that is byte aligned (e.g.,multiple of eight bits) in length. In an example, bit strings may berepresented by tables in which the most significant bit is the leftmostbit of the first line of the table, and the least significant bit is therightmost bit on the last line of the table, and more generally, the bitstring may be read from the left to right and then in the reading orderof the lines. In an example, the bit order of a parameter field within aMAC PDU is represented with the first and most significant bit in theleftmost bit and the last and least significant bit in the rightmostbit.

In an example, a MAC SDU may be a bit string that is byte aligned (e.g.,multiple of eight bits) in length. In an example, a MAC SDU may beincluded into a MAC PDU from the first bit onward.

In an example, a MAC CE may be a bit string that is byte aligned (e.g.,multiple of eight bits) in length.

In an example, a MAC subheader may be a bit string that is byte aligned(e.g., multiple of eight bits) in length. In an example, a MAC subheadermay be placed immediately in front of the corresponding MAC SDU, or MACCE, or padding.

In an example, a MAC entity may ignore a value of reserved bits in a DLMAC PDU.

In an example, a MAC PDU may comprise one or more MAC subPDUs. a MACsubPDU of the one or more MAC subPDUs may comprise at least one of: aMAC subheader only (including padding); a MAC subheader and a MAC SDU; aMAC subheader and a MAC CE; and/or a MAC subheader and padding. In anexample, the MAC SDU may be of variable size. In an example, a MACsubheader may correspond to a MAC SDU, or a MAC CE, or padding.

In an example, a MAC subheader may comprise: an R field with one bit; aF field with one bit in length; a LCID field with multiple bits inlength; a L field with multiple bits in length, when the MAC subheadercorresponds to a MAC SDU, or a variable-sized MAC CE, or padding.

In an example, a MAC subheader may comprise an eight-bit L field. In theexample, the LCID field may have six bits in length, and the L field mayhave eight bits in length. In an example, a MAC subheader may comprise asixteen-bit L field. In the example, the LCID field may have six bits inlength, and the L field may have sixteen bits in length.

In an example, a MAC subheader may comprise: a R field with two bits inlength; and a LCID field with multiple bits in length, when the MACsubheader corresponds to a fixed sized MAC CE, or padding. In anexample, the LCID field may have six bits in length, and the R field mayhave two bits in length.

In an example DL MAC PDU, multiple MAC CEs may be placed together. A MACsubPDU comprising MAC CE may be placed before any MAC subPDU comprisinga MAC SDU, or a MAC subPDU comprising padding.

In an example UL MAC PDU, multiple MAC CEs may be placed together. A MACsubPDU comprising MAC CE may be placed after all MAC subPDU comprising aMAC SDU. The MAC subPDU may be placed before a MAC subPDU comprisingpadding.

In an example, a MAC entity of a gNB may transmit to a MAC entity of awireless device one or more MAC CEs. In an example, multiple LCIDs maybe associated with the one or more MAC CEs. In the example, the one ormore MAC CEs may comprise at least one of: a SP ZP CSI-RS Resource SetActivation/Deactivation MAC CE; a PUCCH spatial relationActivation/Deactivation MAC CE; a SP SRS Activation/Deactivation MAC CE;a SP CSI reporting on PUCCH Activation/Deactivation MAC CE; a TCI StateIndication for UE-specific PDCCH MAC CE; a TCI State Indication forUE-specific PDSCH MAC CE; an Aperiodic CSI Trigger State SubselectionMAC CE; a SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE;a UE contention resolution identity MAC CE; a timing advance command MACCE; a DRX command MAC CE; a Long DRX command MAC CE; a SCellactivation/deactivation MAC CE (1 Octet); a SCellactivation/deactivation MAC CE (4 Octet); and/or a duplicationactivation/deactivation MAC CE. In an example, a MAC CE may have a LCIDin the corresponding MAC subheader. Different MAC CE may have differentLCID in the corresponding MAC subheader. For example, the LCID with111011 in a MAC subheader may indicate a MAC CE associated with the MACsubheader is a long DRX command MAC CE.

In an example, the MAC entity of the wireless device may transmit to theMAC entity of the gNB one or more MAC CEs. In an example, the one ormore MAC CEs may comprise at least one of: a short buffer status report(BSR) MAC CE; a long BSR MAC CE; a C-RNTI MAC CE; a configured grantconfirmation MAC CE; a single entry PHR MAC CE; a multiple entry PHR MACCE; a short truncated BSR; and/or a long truncated BSR. In an example, aMAC CE may have a LCID in the corresponding MAC subheader. Different MACCE may have different LCID in the corresponding MAC subheader. Forexample, the LCID with 111011 in a MAC subheader may indicate a MAC CEassociated with the MAC subheader is a short-truncated command MAC CE.

In a carrier aggregation (CA), two or more component carriers (CCs) maybe aggregated. A wireless device may simultaneously receive or transmiton one or more CCs depending on capabilities of the wireless device. Inan example, the CA may be supported for contiguous CCs. In an example,the CA may be supported for non-contiguous CCs.

When configured with a CA, a wireless device may have one RRC connectionwith a network. During an RRC connectionestablishment/re-establishment/handover, a cell providing a NAS mobilityinformation may be a serving cell. During an RRC connectionre-establishment/handover procedure, a cell providing a security inputmay be a serving cell. In an example, the serving cell may be referredto as a primary cell (PCell). In an example, a gNB may transmit, to awireless device, one or more messages comprising configurationparameters of a plurality of one or more secondary cells (SCells),depending on capabilities of the wireless device.

When configured with CA, a base station and/or a wireless device mayemploy an activation/deactivation mechanism of an SCell for an efficientbattery consumption. When a wireless device is configured with one ormore SCells, a gNB may activate or deactivate at least one of the one ormore SCells. Upon configuration of an SCell, the SCell may bedeactivated.

In an example, a wireless device may activate/deactivate an SCell inresponse to receiving an SCell Activation/Deactivation MAC CE.

In an example, a base station may transmit, to a wireless device, one ormore messages comprising an sCellDeactivationTimer timer. In an example,a wireless device may deactivate an SCell in response to an expiry ofthe sCellDeactivationTimer timer.

When a wireless device receives an SCell Activation/Deactivation MAC CEactivating an SCell, the wireless device may activate the SCell. Inresponse to the activating the SCell, the wireless device may performoperations comprising SRS transmissions on the SCell, CQI/PMI/RI/CRIreporting for the SCell on a PCell, PDCCH monitoring on the SCell, PDCCHmonitoring for the SCell on the PCell, and/or PUCCH transmissions on theSCell.

In an example, in response to the activating the SCell, the wirelessdevice may start or restart an sCellDeactivationTimer timer associatedwith the SCell. The wireless device may start the sCellDeactivationTimertimer in the slot when the SCell Activation/Deactivation MAC CE has beenreceived. In an example, in response to the activating the SCell, thewireless device may (re-)initialize one or more suspended configureduplink grants of a configured grant Type 1 associated with the SCellaccording to a stored configuration. In an example, in response to theactivating the SCell, the wireless device may trigger PHR.

In an example, when a wireless device receives an SCellActivation/Deactivation MAC CE deactivating an activated SCell, thewireless device may deactivate the activated SCell.

In an example, when an sCellDeactivationTimer timer associated with anactivated SCell expires, the wireless device may deactivate theactivated SCell. In response to the deactivating the activated SCell,the wireless device may stop the sCellDeactivationTimer timer associatedwith the activated SCell. In an example, in response to the deactivatingthe activated SCell, the wireless device may clear one or moreconfigured downlink assignments and/or one or more configured uplinkgrant Type 2 associated with the activated SCell. In an example, inresponse to the deactivating the activated SCell, the wireless devicemay further suspend one or more configured uplink grant Type 1associated with the activated SCell. The wireless device may flush HARQbuffers associated with the activated SCell.

In an example, when an SCell is deactivated, a wireless device may notperform operations comprising transmitting SRS on the SCell, reportingCQI/PMI/RI/CRI for the SCell on a PCell, transmitting on UL-SCH on theSCell, transmitting on RACH on the SCell, monitoring at least one firstPDCCH on the SCell, monitoring at least one second PDCCH for the SCellon the PCell, transmitting a PUCCH on the SCell.

In an example, when at least one first PDCCH on an activated SCellindicates an uplink grant or a downlink assignment, a wireless devicemay restart an sCellDeactivationTimer timer associated with theactivated SCell. In an example, when at least one second PDCCH on aserving cell (e.g. a PCell or an SCell configured with PUCCH, i.e. PUCCHSCell) scheduling the activated SCell indicates an uplink grant or adownlink assignment for the activated SCell, a wireless device mayrestart an sCellDeactivationTimer timer associated with the activatedSCell.

In an example, when an SCell is deactivated, if there is an ongoingrandom access procedure on the SCell, a wireless device may abort theongoing random access procedure on the SCell.

In an example, an SCell Activation/Deactivation MAC CE may comprise oneoctet. A first MAC PDU subheader with a first LCID may identify theSCell Activation/Deactivation MAC CE of one octet. The SCellActivation/Deactivation MAC CE of one octet may have a fixed size. TheSCell Activation/Deactivation MAC CE of one octet may comprise a singleoctet. The single octet may comprise a first number of C-fields (e.g.seven) and a second number of R-fields (e.g. one).

In an example, an SCell Activation/Deactivation MAC CE may comprise fouroctets. A second MAC PDU subheader with a second LCID may identify theSCell Activation/Deactivation MAC CE of four octets. The SCellActivation/Deactivation MAC CE of four octets may have a fixed size. TheSCell Activation/Deactivation MAC CE of four octets may comprise fouroctets. The four octets may comprise a third number of C-fields (e.g.31) and a fourth number of R-fields (e.g. 1).

In an example, a C_(i) field may indicate an activation/deactivationstatus of an SCell with an SCell index i, if a SCell with SCell index iis configured. In an example, when the C_(i) field is set to one, anSCell with an SCell index i may be activated. In an example, when theC_(i) field is set to zero, an SCell with an SCell index i may bedeactivated. In an example, if there is no SCell configured with SCellindex i, the wireless device may ignore the C_(i) field. In an example,an R field may indicate a reserved bit. The R field may be set to zero.

A base station may configure a wireless device with one or moreTCI-States by higher layer signaling. A number of the one or more TCIstates may depend on a capability of the wireless device. The wirelessdevice may use the one or more TCI-States to decode a PDSCH according toa detected PDCCH. Each of the one or more TCI-States state may includeone RS set TCI-RS-SetConfig. The one RS set TCI-RS-SetConfig may containone or more parameters. In an example, the one or more parameters may beused to configure quasi co-location relationship between one or morereference signals in the RS set and the DM-RS port group of the PDSCH.The one RS set may contain a reference to either one or two DL RSs andan associated quasi co-location type (QCL-Type) for each one configuredby the higher layer parameter QCL-Type. For the case of the two DL RSs,the QCL types may not be the same. In an example, the references of thetwo DL RSs may be to the same DL RS or different DL RSs. The quasico-location types indicated to the UE may be based on a higher layerparameter QCL-Type. The higher layer parameter QCL-Type may take one ora combination of the following types: QCL-TypeA′: {Doppler shift,Doppler spread, average delay, delay spread}; QCL-TypeB′: {Dopplershift, Doppler spread}; QCL-TypeC′: {average delay, Doppler shift} andQCL-TypeD′: {Spatial Rx parameter}.

In an example, a wireless device may receive an activation command. Theactivation command may be used to map one or more TCI states to one ormore codepoints of the DCI field Transmission Configuration Indication(TCI). After the wireless device receives a higher layer configurationof TCI states and before reception of the activation command, thewireless device may assume that one or more antenna ports of one DM-RSport group of PDSCH of a serving cell are spatially quasi co-locatedwith an SSB. In an example, the SSB may be determined in an initialaccess procedure with respect to Doppler shift, Doppler spread, averagedelay, delay spread, spatial Rx parameters, where applicable.

In an example, a wireless device may be configured, by a base station,with a higher layer parameter TCI-PresentInDCI. When the higher layerparameter TCI-PresentInDCI is set as ‘Enabled’ for a CORESET schedulinga PDSCH, the wireless device may assume that the TCI field is present ina DL DCI of a PDCCH transmitted on the CORESET. When the higher layerparameter TCI-PresentInDCI is set as ‘Disabled’ for a CORESET schedulinga PDSCH or the PDSCH is scheduled by a DCI format 1_0, for determiningPDSCH antenna port quasi co-location, the wireless device may assumethat the TCI state for the PDSCH is identical to the TCI state appliedfor the CORESET used for the PDCCH transmission.

When the higher layer parameter TCI-PresentinDCI is set as ‘Enabled’,the wireless device may use one or more TCI-States according to a valueof the ‘Transmission Configuration Indication’ field in the detectedPDCCH with DCI for determining PDSCH antenna port quasi co-location. Thewireless device may assume that the antenna ports of one DM-RS portgroup of PDSCH of a serving cell are quasi co-located with one or moreRS(s) in the RS set with respect to the QCL type parameter(s) given bythe indicated TCI state if the time offset between the reception of theDL DCI and the corresponding PDSCH is equal to or greater than athreshold Threshold-Sched-Offset. In an example, the threshold may bebased on UE capability. When the higher layer parameterTCI-PresentInDCI=‘Enabled’ and the higher layer parameterTCI-PresentInDCI=‘Disabled’, if the offset between the reception of theDL DCI and the corresponding PDSCH is less than the thresholdThreshold-Sched-Offset, the wireless device may assume that the antennaports of one DM-RS port group of PDSCH of a serving cell are quasico-located based on the TCI state used for PDCCH quasi co-locationindication of the lowest CORESET-ID in the latest slot in which one ormore CORESETs are configured for the UE. If all configured TCI states donot contain QCL-TypeD′, the wireless device may obtain the other QCLassumptions from the indicated TCI states for its scheduled PDSCHirrespective of the time offset between the reception of the DL DCI andthe corresponding PDSCH.

A gNB and/or a wireless device may have multiple antenna, to support atransmission with high data rate in a NR system. When configured withmultiple antennas, a wireless device may perform one or more beammanagement procedures, as shown in FIG. 9B.

A wireless device may perform a downlink beam management based on one ormore CSI-RS s, and/or one or more SSBs. In a beam management procedure,a wireless device may measure a channel quality of a beam pair link. Thebeam pair link may comprise a transmitting beam from a gNB and areceiving beam at the wireless device. When configured with multiplebeams associated with multiple CSI-RSs or SSBs, a wireless device maymeasure the multiple beam pair links between the gNB and the wirelessdevice.

In an example, a wireless device may transmit one or more beammanagement reports to a gNB. In a beam management report, the wirelessdevice may indicate one or more beam pair quality parameters, comprisingat least, one or more beam identifications; RSRP; PMI/CQI/RI of at leasta subset of configured multiple beams.

In an example, a gNB and/or a wireless device may perform a downlinkbeam management procedure on one or multiple Transmission and ReceivingPoint (TRPs), as shown in FIG. 9B. Based on a wireless device's beammanagement report, a gNB may transmit to the wireless device a signalindicating that a new beam pair link is a serving beam. The gNB maytransmit PDCCH and PDSCH to the wireless device using the serving beam.

In an example, a wireless device or a gNB may trigger a beam failurerecovery mechanism. A wireless device may trigger a beam failurerecovery (BFR) procedure, e.g., when at least a beam failure occurs. Inan example, a beam failure may occur when quality of beam pair link(s)of at least one PDCCH falls below a threshold. The threshold may be aRSRP value (e.g., −140 dbm, −110 dbm) or a SINR value (e.g., −3 dB, −1dB), which may be configured in a RRC message.

FIG. 16A shows example of a first beam failure scenario. In the example,a gNB may transmit a PDCCH from a transmission (Tx) beam to a receiving(Rx) beam of a wireless device from a TRP. When the PDCCH on the beampair link (between the Tx beam of the gNB and the Rx beam of thewireless device) have a lower-than-threshold RSRP/SINR value due to thebeam pair link being blocked (e.g., by a moving car or a building), thegNB and the wireless device may start a beam failure recovery procedureon the TRP.

FIG. 16B shows example of a second beam failure scenario. In theexample, the gNB may transmit a PDCCH from a beam to a wireless devicefrom a first TRP. When the PDCCH on the beam is blocked, the gNB and thewireless device may start a beam failure recovery procedure on a newbeam on a second TRP.

In an example, a wireless device may measure quality of beam pair linkusing one or more RSs. The one or more RSs may be one or more SSBs, orone or more CSI-RS resources. A CSI-RS resource may be identified by aCSI-RS resource index (CRI). In an example, quality of beam pair linkmay be defined as a RSRP value, or a reference signal received quality(e.g. RSRQ) value, and/or a CSI (e.g., SINR) value measured on RSresources. In an example, a gNB may indicate whether an RS resource,used for measuring beam pair link quality, is QCLed (Quasi-Co-Located)with DM-RSs of a PDCCH. The RS resource and the DM-RSs of the PDCCH maybe called QCLed when the channel characteristics from a transmission onan RS to a wireless device, and that from a transmission on a PDCCH tothe wireless device, are similar or same under a configured criterion.In an example, The RS resource and the DM-RSs of the PDCCH may be calledQCLed when doppler shift and/or doppler shift of the channel from atransmission on an RS to a wireless device, and that from a transmissionon a PDCCH to the wireless device, are same.

In an example, a wireless device may monitor PDCCH on M beam (e.g. 2, 4,8) pair links simultaneously, where M≥1 and the value of M may depend atleast on capability of the wireless device. In an example, monitoring aPDCCH may comprise detecting a DCI via the PDCCH transmitted on commonsearch spaces and/or wireless device specific search spaces. In anexample, monitoring multiple beam pair links may increase robustnessagainst beam pair link blocking. In an example, a gNB may transmit oneor more messages comprising parameters indicating a wireless device tomonitor PDCCH on different beam pair link(s) in different OFDM symbols.

In an example, a gNB may transmit one or more RRC messages or MAC CEscomprising parameters indicating Rx beam setting of a wireless devicefor monitoring PDCCH on multiple beam pair links. A gNB may transmit anindication of spatial QCL between an DL RS antenna port(s) and DL RSantenna port(s) for demodulation of DL control channel. In an example,the indication may be a parameter in a MAC CE, or an RRC message, or aDCI, and/or combination of these signaling.

In an example, for reception of data packet on a PDSCH, a gNB mayindicate spatial QCL parameters between DL RS antenna port(s) and DM-RSantenna port(s) of DL data channel. A gNB may transmit DCI comprisingparameters indicating the RS antenna port(s) QCL-ed with DM-RS antennaport(s).

In an example, when a gNB transmits a signal indicating QCL parametersbetween CSI-RS and DM-RS for PDCCH, a wireless device may measure a beampair link quality based on CSI-RSs QCLed with DM-RS for PDCCH. In anexample, when multiple contiguous beam failures occur, the wirelessdevice may start a BFR procedure.

In an example, a wireless device transmits a BFR signal on an uplinkphysical channel to a gNB when starting a BFR procedure. The gNB maytransmit a DCI via a PDCCH in a coreset in response to receiving the BFRsignal on the uplink physical channel. The wireless may consider the BFRprocedure successfully completed when receiving the DCI via the PDCCH inthe coreset.

In an example, a gNB may transmit one or more messages comprisingconfiguration parameters of an uplink physical channel or signal fortransmitting a beam failure recovery request. The uplink physicalchannel or signal may be based on one of: a contention-free PRACH(BFR-PRACH), which may be a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (BFR-PUCCH); and/or a contention-basedPRACH resource (CF-PRACH). Combinations of these candidatesignal/channels may be configured by the gNB. In an example, whenconfigured with multiple resources for a BFR signal, a wireless devicemay autonomously select a first resource for transmitting the BFRsignal. In an example, when configured with a BFR-PRACH resource, aBFR-PUCCH resource, and a CF-PRACH resource, the wireless device mayselect the BFR-PRACH resource for transmitting the BFR signal. In anexample, when configured with a BFR-PRACH resource, a BFR-PUCCHresource, and a CF-PRACH resource, the gNB may transmit a message to thewireless device indicating a resource for transmitting the BFR signal.

In an example, a gNB may transmit a response to a wireless device afterreceiving one or more BFR signals. The response may comprise the CRIassociated with the candidate beam the wireless device indicates in theone or multiple BFR signals.

In an NR system, when configured with multiple beams, a gNB and/or awireless device may perform one or more beam management procedure. Forexample, the wireless device may perform a BFR procedure, if one or morebeam pair links between the gNB and the wireless device fail.

FIG. 17 shows an example flowchart of the BFR procedure. A wirelessdevice may receive one or more RRC messages comprising BFR parameters.The one or more RRC messages may comprise an RRC message (e.g. RRCconnection reconfiguration message, or RRC connection reestablishmentmessage, or RRC connection setup message). The wireless device maydetect at least one beam failure according to at least one of BFRparameters. The wireless device may start a first timer if configured inresponse to detecting the at least one beam failure. The wireless devicemay select a selected beam in response to detecting the at least onebeam failure. The selected beam may be a beam with good channel quality(e.g., RSRP, SINR, or BLER) from a set of candidate beams. The candidatebeams may be identified by a set of reference signals (e.g., SSBs, orCSI-RS s). The wireless device may transmit at least a first BFR signalto a gNB in response to the selecting the selected beam. The at leastfirst BFR signal may be associated with the selected beam. The at leastfirst BFR signal may be a preamble transmitted on a PRACH resource, or abeam failure request (e.g., similar to scheduling request) signaltransmitted on a PUCCH resource, or a beam indication transmitted on aPUCCH/PUSCH resource. The wireless device may transmit the at leastfirst BFR signal with a transmission beam corresponding to a receivingbeam associated with the selected beam. The wireless device may start aresponse window in response to transmitting the at least first BFRsignal. In an example, the response window may be a timer with a valueconfigured by the gNB. When the response window is running, the wirelessdevice may monitor a PDCCH in a first coreset. The first coreset may beassociated with the BFR procedure. In an example, the wireless devicemay monitor the PDCCH in the first coreset in condition of transmittingthe at least first BFR signal. The wireless device may receive a firstDCI via the PDCCH in the first coreset when the response window isrunning. The wireless device may consider the BFR procedure successfullycompleted when receiving the first DCI via the PDCCH in the firstcoreset before the response window expires. The wireless device may stopthe first timer if configured in response to the BFR proceduresuccessfully being completed. The wireless device may stop the responsewindow in response to the BFR procedure successfully being completed.

In an example, when the response window expires, and the wireless devicedoes not receive the DCI, the wireless device may increment atransmission number, wherein, the transmission number is initialized toa first number (e.g., 0) before the BFR procedure is triggered. If thetransmission number indicates a number less than the configured maximumtransmission number, the wireless device may repeat one or more actionscomprising at least one of: a BFR signal transmission; starting theresponse window; monitoring the PDCCH; incrementing the transmissionnumber if no response received during the response window is running. Ifthe transmission number indicates a number equal or greater than theconfigured maximum transmission number, the wireless device may declarethe BFR procedure is unsuccessfully completed.

A MAC entity of a wireless device may be configured by an RRC with abeam failure recovery procedure. The beam failure recovery procedure maybe used for indicating to a serving base station of a new (e.g.,candidate) SSB or CSI-RS when a beam failure is detected. The beamfailure may be detected on one or more serving SSB(s)/CSI-RS(s) of theserving base station. In an example, the beam failure may be detected bycounting a beam failure instance indication from a lower layer of thewireless device (e.g. PHY layer) to the MAC entity.

In an example, an RRC may configure a wireless device with one or moreparameters in BeamFailureRecoveryConfig for a beam failure detection andrecovery procedure. The one or more parameters may comprise at least:beamFailureInstanceMaxCount for a beam failure detection;beamFailureDetectionTimer for the beam failure detection;beamFailureRecoveryTimer for the beam failure recovery procedure;rsrp-ThresholdSSB: an RSRP threshold for a beam failure recovery;PowerRampingStep for the beam failure recovery;preambleReceivedTargetPower for the beam failure recovery; preambleTxMaxfor the beam failure recovery; and ra-ResponseWindow. Thera-ResponseWindow may be a time window to monitor one or more responsesfor the beam failure recovery using a contention-free Random Accesspreamble.

FIG. 18 shows an example of beam failure instance (BFI) indication. Inan example, a wireless device may use at least one UE variable for abeam failure detection. BFI_COUNTER may be one of the at least one UEvariable. The BFI_COUNTER may be a counter for a beam failure instanceindication. The BFI_COUNTER may be initially set to zero.

In an example, if a MAC entity of a wireless device receives a beamfailure instance indication from a lower layer (e.g. PHY) of thewireless device, the wireless device may start or restartbeamFailureDetectionTimer (e.g., BFR timer in FIG. 18). In addition tostarting or restarting the beamFailureDetectionTimer, the wirelessdevice may increment BFI_COUNTER by one (e.g., at time T, 2T, 5T in FIG.18).

In an example, if configured with BeamFailureRecoveryConfig, thewireless device may initiate a random access procedure (e.g. on anSpCell) for a beam failure recovery in response to the BFI_COUNTER beingequal or greater than the beamFailureInstanceMaxCount. In an example, ifconfigured with BeamFailureRecoveryConfig, the wireless device may startthe beamFailureRecoveryTimer (if configured) in response to theBFI_COUNTER being equal or greater than the beamFailureInstanceMaxCount.The wireless device may apply the one or more parameters in theBeamFailureRecoveryConfig (e.g., powerRampingStep,preambleReceivedTargetPower, and preambleTransMax) in response to theinitiating the random access procedure. In an example, the random accessprocedure may be contention-free random access procedure.

In an example, if not configured with BeamFailureRecoveryConfig, thewireless device may initiate a random access procedure (e.g. on anSpCell) for a beam failure recovery in response to the BFI_COUNTER beingequal or greater than the beamFailureInstanceMaxCount. In an example,the random access procedure may be contention-based random accessprocedure.

In an example, in FIG. 18, the wireless device may initiate the randomaccess procedure at time 6T, when the first number (e.g., 3) is reached.

In an example, if the beamFailureDetectionTimer expires, the wirelessdevice may set the BFI_COUNTER to zero (e.g., in FIG. 18, between time3T and 4T).

In an example, if the random access procedure (e.g., contention-freerandom access or contention-based random access) is successfullycompleted, the wireless device may consider the beam failure recoveryprocedure successfully completed.

In an example, if the random access procedure (e.g., contention-freerandom access) is successfully completed, the wireless device may stopthe beamFailureRecoveryTimer (if configured).

If a MAC entity of a wireless device transmits a contention-free randomaccess preamble for a beam failure recovery request, the MAC entity maystart ra-ResponseWindow at a first PDCCH occasion from the end of thetransmitting the contention-free random access preamble. Thera-ResponseWindow may be configured in BeamFailureRecoveryConfig. Whilethe ra-ResponseWindow is running, the wireless device may monitor atleast one PDCCH (e.g. of an SpCell) for a response to the beam failurerecovery request. The beam failure recovery request may be identified bya C-RNTI.

In an example, if a MAC entity of a wireless device receives, from alower layer of the wireless device, a notification of a reception of atleast one PDCCH transmission and if the at least one PDCCH transmissionis addressed to a C-RNTI and if a contention-free random access preamblefor a beam failure recovery request is transmitted by the MAC entity,the wireless device may consider a random access procedure successfullycompleted.

In an example, a wireless device may initiate a contention-based randomaccess preamble for a beam failure recovery request. When the wirelessdevice transmits Msg3, a MAC entity of the wireless device may startra-ContentionResolutionTimer. The ra-ContentionResolutionTimer may beconfigured by RRC. In response to the starting thera-ContentionResolutionTimer, the wireless device may monitor at leastone PDCCH while the ra-ContentionResolutionTimer is running. In anexample, if the MAC entity receives, from a lower layer of the wirelessdevice, a notification of a reception of the at least one PDCCHtransmission; if a C-RNTI MAC-CE is included in the Msg3; if a randomaccess procedure is initiated for a beam failure recovery and the atleast one PDCCH transmission is addressed to a C-RNTI of the wirelessdevice, the wireless device may consider the random access proceduresuccessfully completed. In response to the random access procedure beingsuccessfully completed, the wireless device may stop thera-ContentionResolutionTimer.

In an example, if a random access procedure of a beam failure recoveryis successfully completed, the wireless device may consider the beamfailure recovery successfully completed.

A wireless device may be configured, for a serving cell, with a firstset of periodic CSI-RS resource configuration indexes by higher layerparameter Beam-Failure-Detection-RS-ResourceConfig (e.g.,failureDetectionResources). The wireless device may further beconfigured with a second set of CSI-RS resource configuration indexesand/or SS/PBCH block indexes by higher layer parameterCandidate-Beam-RS-List (e.g., candidateBeamRSList). In an example, thefirst set and/or the second set may be used for radio link qualitymeasurements on the serving cell. If a wireless device is not providedwith higher layer parameter Beam-Failure-Detection-RS-ResourceConfig,the wireless device may determine a first set to include SS/PBCH blockindexes and periodic CSI-RS resource configuration indexes. In anexample, the SS/PBCH block indexes and the periodic CSI-RS resourceconfiguration indexes may be with same values as one or more RS indexesin one or more RS sets. In an example, the one or more RS indexes in theone or more RS sets may be indicated by one or more TCI states. In anexample, the one or more TCI states may be used for respective controlresource sets that the wireless device is configured for monitoringPDCCH. The wireless device may expect a single port RS in the first set.

In an example, the wireless device may expect the first set of periodicCSI-RS resource configurations to include up to two RS indexes. In anexample, if the first set of periodic CSI-RS resource configurationsincludes two RS indexes, the first set of periodic CSI-RS resourceconfigurations may include one or more RS indexes with QCL-TypeDconfiguration. In an example, the wireless device may expect a singleport RS in the first set of periodic CSI-RS resource configurations.

In an example, a first threshold (e.g. Qout,LR) may correspond to afirst default value of higher layer parameter RLM-IS-OOS-thresholdConfig(e.g., rlmInSyncOutOfSyncThreshold). In an example, a second threshold(e.g. Qin,LR) may correspond to a second default value of higher layerparameter Beam-failure-candidate-beam-threshold (e.g.,rsrp-ThresholdSSB).

In an example, a physical layer in the wireless device may assess afirst radio link quality according to the first set of periodic CSI-RSresource configurations against the first threshold. For the first set,the wireless device may assess the first radio link quality according toperiodic CSI-RS resource configurations or SS/PBCH blocks. In anexample, the periodic CSI-RS resource configurations or the SS/PBCHblocks may be associated (e.g. quasi co-located) with at least one DM-RSof PDCCH receptions monitored by the wireless device.

In an example, the wireless device may apply the second threshold to afirst L1-RSRP measurement obtained from one or more SS/PBCH blocks. Inan example, the wireless device may apply the second threshold to asecond L1-RSRP measurement obtained for one or more periodic CSI-RSresources after scaling a respective CSI-RS reception power with a valueprovided by higher layer parameter PC_SS (e.g., powerControlOffsetSS).

In an example, a wireless device may assess the first radio link qualityof the first set. A physical layer in the wireless device may provide anindication to higher layers (e.g. MAC) when the first radio link qualityfor all corresponding resource configurations in the first set is worsethan the first threshold. In an example, the wireless device may use theall corresponding resource configurations in the first set to assess thefirst radio link quality. The physical layer may inform the higherlayers (e.g. MAC, RRC) when the first radio link quality is worse thanthe first threshold with a first periodicity. The first periodicity maybe determined by the maximum between the shortest periodicity ofperiodic CSI-RS configurations or SS/PBCH blocks in the first set and X(e.g. 2 msec). In an example, the wireless device may assess theperiodic CSI-RS configurations or the SS/PBCH blocks for the first radiolink quality.

In an example, in response to a request from higher layers (e.g. MAC), awireless device may provide to the higher layers the periodic CSI-RSconfiguration indexes and/or the SS/PBCH blocks indexes from the secondset. The wireless device may further provide, to the higher layers,corresponding L1-RSRP measurements that are larger than or equal to thesecond threshold.

A wireless device may be provided/configured with a control resource set(coreset) through a link to a search space set. In an example, thesearch space set may be provided by higher layer parameterrecoverySearchSpaceId. The search space may be used for monitoring PDCCHin the control resource set. In an example, if the wireless device isprovided by the higher layer parameter recoverySearchSpaceId, thewireless device may not expect to be provided with a second search spaceset for monitoring the coreset. In an example, the coreset may beassociated with the search space set provided by the higher layerparameter recoverySearchSpaceId.

The wireless device may receive from higher layers (e.g. MAC), byparameter PRACH-ResourceDedicatedBFR, a configuration for a PRACHtransmission. For the PRACH transmission in slot n and according toantenna port quasi co-location parameters associated with periodicCSI-RS configuration or SS/PBCH block with a first RS index, thewireless device may monitor the PDCCH in a search space set (e.g.,provided by the higher layer parameter recoverySearchSpaceId) fordetection of a DCI format starting from slot n+4 within a window. Thewindow may be configured by higher layer parameterBeamFailureRecoveryConfig. The DCI format may be with CRC scrambled byC-RNTI. In an example, the first RS index may be provided by the higherlayers.

In an example, for the PDCCH monitoring and for the corresponding PDSCHreception, the wireless device may assume the same antenna portquasi-collocation parameters with the first RS index (e.g. as formonitoring the PDCCH) until the wireless device receives by higherlayers an activation for a TCI state or a parameterTCI-StatesPDCCH-ToAddlist and/or TCI-StatesPDCCH-ToReleaseList

In an example, after the wireless device detects the DCI format with CRCscrambled by the C-RNTI in the search space set (e.g., provided by thehigher layer parameter recoverySearchSpaceId), the wireless device maymonitor PDCCH candidates in the search space set until the wirelessdevice receives a MAC-CE activation command for a TCI state or a higherlayer parameters TCI-StatesPDCCH-ToAddlist and/orTCI-StatesPDCCH-ToReleaseList.

In an example, if the wireless device is not provided with a coreset fora search space set (e.g., provided by a higher layer parameterrecoverySearchSpaceId), the wireless device may not expect to receive aPDCCH order triggering a PRACH transmission. In an example, the wirelessdevice may initiate a contention-based random-access procedure for abeam failure recovery in response to not being provided with thecoreset.

In an example, if the wireless device is not provided with a higherlayer parameter recoverySearchSpaceId, the wireless device may notexpect to receive a PDCCH order triggering a PRACH transmission. In anexample, the wireless device may initiate a contention-basedrandom-access procedure for a beam failure recovery in response to notbeing provided with the higher layer parameter recoverySearchSpaceId.

A base station (gNB) may configure a wireless device (UE) with one ormore uplink (UL) bandwidth parts (BWPs) and one or more downlink (DL)BWPs to enable bandwidth adaptation (BA) on a PCell. If carrieraggregation is configured, the gNB may configure the UE with at leastone or more DL BWP(s) (i.e. there may be no UL BWPS in the UL) to enableBA on an SCell. For the PCell, a first initial BWP may be a first BWPused for initial access. For the SCell, a second initial BWP is a secondBWP configured for the UE to first operate at the SCell when the SCellis activated.

In paired spectrum (e.g. FDD), a wireless device can switch an active DLBWP and an active UL BWP independently. In unpaired spectrum (e.g. TDD),a wireless device can switch an active DL BWP and an active UL BWPsimultaneously. Switching between configured BWPs may happen by means ofa DCI or an inactivity timer. When the inactivity timer is configuredfor a serving cell, an expiry of the inactivity timer associated to thatcell may switch an active BWP to a default BWP. The default BWP may beconfigured by the network.

In an example, for FDD systems, when configured with BA, one UL BWP foreach uplink carrier and one DL BWP may be active at a time in an activeserving cell. In an example, for TDD systems, one DL/UL BWP pair may beactive at a time in an active serving cell. Operating on the one UL BWPand the one DL BWP (or the one DL/UL pair) may enable reasonable UEbattery consumption. BWPs other than the one UL BWP and the one DL BWPthat the UE may be configured with may be deactivated. On deactivatedBWPs, the UE may not monitor PDCCH, may not transmit on PUCCH, PRACH andUL-SCH.

In an example, a Serving Cell may be configured with at most a firstnumber (e.g., four) BWPs. In an example, for an activated Serving Cell,there may be one active BWP at any point in time.

In an example, a BWP switching for a serving cell (e.g., PCell, SCell)may be used to activate an inactive BWP and deactivate an active BWP ata time. In an example, the BWP switching may be controlled by a PDCCHindicating a downlink assignment or an uplink grant. In an example, theBWP switching may be controlled by an inactivity timer (e.g.bwpInactivityTimer). In an example, the BWP switching may be controlledby an RRC signaling. In an example, the BWP switching may be controlledby a MAC entity in response to initiating a random access procedure.Upon addition of an SpCell or activation of an SCell, a DL BWP indicatedby firstActiveDownlinkBWP-ID (e.g., included in RRC signaling) and an ULBWP indicated by firstActiveUplinkBWP-ID (e.g., included in RRCsignaling) are active without receiving a PDCCH indicating a downlinkassignment or an uplink grant. The active BWP for a serving cell may beindicated by RRC and/or PDCCH. In an example, for unpaired spectrum(e.g., time-division-duplex (TDD)), a DL BWP may be paired with an ULBWP, and BWP switching may be common for both UL and DL.

In an example, for an activated serving cell (e.g., PCell, SCell)configured with one or more BWPs, if the BWP is activated, a MAC entitymay perform at least one of: transmitting on UL-SCH on the one or moreBWPs; transmitting on RACH on the one or more BWPs; monitoring a PDCCHon the one or more BWPs; transmitting SRS on the one or more BWPs;transmitting PUCCH on the one or more BWPs; receiving DL-SCH on the oneor more BWPs; (re-) initializing any suspended configured uplink grantsof configured grant Type 1 on the one or more BWPs according to a storedconfiguration, if any, and to start in a symbol based on some procedure.

In an example, for an activated serving cell (e.g., PCell, SCell)configured with one or more BWPs, if the BWP is deactivated, a MACentity may not transmit on UL-SCH on the one or more BWPs; may nottransmit on RACH on the one or more BWPs; may not monitor a PDCCH on theone or more BWPs; may not report CSI for the one or more BWPs; may nottransmit PUCCH on the one or more BWPs; may not transmit SRS on the oneor more BWPs, may not receive DL-SCH on the one or more BWPs; may clearany configured downlink assignment and configured uplink grant ofconfigured grant Type 2 on the one or more BWPs; may suspend anyconfigured uplink grant of configured Type 1 on the one or more BWPs(e.g., inactive BWPs).

In an example, upon initiation of a random access procedure (e.g.,contention-based random access, contention-free random access) on aserving cell, if PRACH occasions are configured for an active UL BWP, ofthe serving cell, with an uplink BWP ID; and if the serving cell is anSpCell; and if a downlink BWP ID of an active DL BWP of the serving cellis not the same as the uplink BWP ID, a MAC entity may switch from theactive DL BWP to a DL BWP with a second downlink BWP ID same as theuplink BWP ID. In response to the switching, the MAC entity may performthe random access procedure on the DL BWP of the serving cell (e.g.,SpCell) and the active UL BWP of the serving cell.

In an example, upon initiation of a random access procedure (e.g.,contention-based random access, contention-free random access) on aserving cell (e.g., SCell), if PRACH occasions are configured for anactive UL BWP of the serving cell; and if the serving cell is not anSpCell, a MAC entity may perform the random access procedure on anactive DL BWP of an SpCell and an active UL BWP of the serving cell.

In an example, upon initiation of a random access procedure on a servingcell, if PRACH resources are not configured for an active UL BWP of theserving cell, a MAC entity may switch the active UL BWP to an uplink BWP(initial uplink BWP). In an example, the uplink BWP may be indicated byRRC signaling (e.g., initialULBWP). In an example, if the serving cellis an SpCell, the MAC entity may switch an active DL BWP to a downlinkBWP (e.g., initial downlink BWP). In an example, the downlink BWP may beindicated by RRC signaling (e.g., initialDLBWP). In response to theswitching, the MAC entity may perform the random access procedure on theuplink BWP and the downlink BWP.

In an example, upon initiation of a random access procedure on a servingcell, if PRACH resources are not configured for an active UL BWP of theserving cell (e.g., SCell), a MAC entity may switch the active UL BWP toan uplink BWP (initial uplink BWP). In an example, the uplink BWP may beindicated by RRC signaling (e.g., initialULBWP). In an example, if theserving cell is not an SpCell, the MAC entity may perform the randomaccess procedure on the uplink BWP and an active downlink BWP of anSpCell.

In an example, if a MAC entity receives a PDCCH for a BWP switching fora serving cell while a random access procedure associated with theserving cell is not ongoing, a UE may perform the BWP switching to a BWPindicated by the PDCCH.

In an example, if a MAC entity receives a PDCCH for a BWP switching fora serving cell while a random access procedure is ongoing in the MACentity, it may be up to UE implementation whether to switch BWP orignore the PDCCH for the BWP switching. In an example, if the PDCCH forthe BWP switching is addressed to C-RNTI for a successful completion ofthe random access procedure, the UE may perform the BWP switching to anew BWP indicated by the PDCCH.

In an example, if the MAC entity decides to perform the BWP switching tothe new BWP (indicated by the PDCCH) in response to the receiving thePDCCH (other than successful contention resolution), the MAC entity maystop the ongoing random access procedure and initiate a second randomaccess procedure on the new BWP. In an example, if the MAC decides toignore the PDCCH for the BWP switching, the MAC entity may continue withthe ongoing random access procedure on an active BWP.

In an example, if a BWP inactivity timer is configured, for an activatedserving cell, if a default DL BWP is configured (e.g., via RRC signalingincluding defaultDownlinkBWP parameter), and an active DL BWP is not aBWP indicated by the default DL BWP; or if the default DL BWP is notconfigured, and an active DL BWP is not the initial downlink BWP (e.g.,via RRC signaling including initialDownlinkBWP parameter): if a PDCCHaddressed to C-RNTI or CS-RNTI indicating downlink assignment or uplinkgrant is received on the active BWP or for the active BWP: if there isnot an ongoing random access procedure associated with the activatedserving cell, the MAC entity may start or restart the BWP inactivitytimer associated with the active DL BWP.

In an example, if a BWP inactivity timer is configured, for an activatedserving cell, if a default DL BWP is configured, and an active DL BWP isnot a BWP indicated by the default DL BWP; or if the default DL BWP isnot configured, and an active DL BWP is not the initial downlink BWP: ifa MAC-PDU is transmitted in a configured uplink grant or received in aconfigured downlink assignment; if there is not an ongoing random accessprocedure associated with the activated serving cell, the MAC entity maystart or restart the BWP inactivity timer associated with the active DLBWP.

In an example, if a BWP inactivity timer is configured, for an activatedserving cell, if a default DL BWP is configured, and an active DL BWP isnot a BWP indicated by the default DL BWP; or if the default DL BWP isnot configured, and an active DL BWP is not the initial downlink BWP: ifa PDCCH addressed to C-RNTI or CS-RNTI indicating downlink assignment oruplink grant is received on the active BWP or for the active BWP; or ifa MAC-PDU is transmitted in a configured uplink grant or received in aconfigured downlink assignment: if an ongoing random access procedureassociated with the activated serving cell is successfully completed inresponse to receiving a PDCCH addressed to C-RNTI, the MAC entity maystart or restart the BWP inactivity timer associated with the active DLBWP.

In an example, if a BWP inactivity timer is configured, for an activatedserving cell, if a default DL BWP is configured, and an active DL BWP isnot a BWP indicated by the default DL BWP; or if the default DL BWP isnot configured, and the active DL BWP is not the initial downlink BWP:if a PDCCH for a BWP switching is received on the active DL BWP, a MACentity may start or restart the BWP inactivity timer associated with theactive DL BWP in response to switching the active BWP.

In an example, if BWP inactivity timer is configured, for an activatedserving cell, if the default DL BWP is configured, and the active DL BWPis not the BWP indicated by the default DL BWP; or if the default DL BWPis not configured, and the active DL BWP is not the initial downlinkBWP: if random access procedure is initiated on the activated servingcell, the MAC entity may stop the BWP inactivity timer (if running)associated with the active DL BWP of the activated serving cell. If theactivated serving cell is an SCell (other than a PSCell), the MAC entitymay stop a second BWP inactivity timer (if running) associated with asecond active DL BWP of an SpCell.

In an example, if BWP inactivity timer is configured, for an activatedserving cell, if the default DL BWP is configured, and the active DL BWPis not the BWP indicated by the default DL BWP; or if the default DL BWPis not configured, and the active DL BWP is not the initial downlinkBWP: if BWP inactivity timer associated with the active DL BWP expires:if the default DL BWP is configured, the MAC entity may perform BWPswitching to a BWP indicated by the default DL BWP. Otherwise, the MACentity may perform BWP switching to the initial downlink BWP.

In an example, a UE may be configured for operation in bandwidth parts(BWPs) of a serving cell. In an example, the UE may be configured byhigher layers for the serving cell a first set of (e.g., at most four)BWPs for receptions by the UE (e.g., DL BWP set) in a downlink (DL)bandwidth by a parameter DL-BWP (e.g., BWP-Downlink) for the servingcell. In an example, the UE may be configured with a second set of(e.g., at most four) BWPs for transmissions by the UE (e.g., UL BWP set)in an uplink (UL) bandwidth by a parameter UL-BWP (e.g., BWP-Uplink) forthe serving cell.

In an example, an initial active DL BWP may be defined, for example, bya location and a number of contiguous PRBs, a subcarrier spacing, and acyclic prefix, for the control resource set for Type0-PDCCH commonsearch space. In an example, for operation on a primary cell or on asecondary cell, a UE may be provided with an initial active UL BWP by ahigher layer parameter (e.g., initialuplinkBWP). In an example, if awireless device is configured with a supplementary carrier, the wirelessdevice can be provided with an initial uplink BWP on the supplementarycarrier by a second higher layer parameter (e.g., initialUplinkBWP insupplementaryUplink).

In an example, if a UE has a dedicated BWP configuration, the UE may beprovided by a higher layer parameter (e.g., firstActiveDownlinkBWP-Id).The higher layer parameter may indicate a first active DL BWP forreceptions.

In an example, if a UE has a dedicated BWP configuration, the UE may beprovided by a second higher layer parameter (e.g.,firstActiveUplinkBWP-Id). The higher layer parameter may indicate afirst active UL BWP for transmissions on the primary cell.

In an example, for a DL BWP or an UL BWP in a first set of DL BWPs or asecond set of UL BWPs, respectively, the UE may be configured with atleast one of the following parameters for a serving cell: a subcarrierspacing provided by higher layer parameter subcarrierSpacing orUL-BWP-mu; a cyclic prefix provided by higher layer parametercyclicPrefix; an index in the first set of DL BWPs or in the second setof UL BWPs by respective higher layer parameters bwp-Id (e.g.,DL-BWP-ID, UL-BWP-ID); a third set of BWP-common and a fourth set ofBWP-dedicated parameters by a higher layer parameter bwp-Common and ahigher layer parameter bwp-Dedicated, respectively.

In an example, for an unpaired spectrum operation, a DL BWP from a firstset of configured DL BWPs with a DL BWP index provided by higher layerparameter bwp-ID for the DL BWP may be paired/linked with an UL BWP froma second set of configured UL BWPs with an UL BWP index provided by ahigher layer parameter bwp-ID for the UL BWP when the DL BWP index andthe UL BWP index are equal.

In an example, for an unpaired spectrum operation, the UE may not expectto receive a configuration where the center frequency for the DL BWP isdifferent than the center frequency for the UL BWP when the DL BWP indexof the DL BWP is equal to the UL BWP index of the UL BWP.

In an example, for a DL BWP in a first set of DL BWPs on a primary cell,a UE may be configured with control resource sets for every type ofcommon search space and for UE-specific search space. In an example, theUE may not expect to be configured without a common search space on theprimary cell (or on the PSCell), in the DL BWP (e.g., active DL BWP).

In an example, for an UL BWP in a second set of UL BWPs, the UE may beconfigured with one or more resource sets for PUCCH transmissions. In anexample, a UE may receive PDCCH and PDSCH in a DL BWP according to aconfigured subcarrier spacing and CP length for the DL BWP.

In an example, a UE may transmit PUCCH and PUSCH in an UL BWP accordingto a configured subcarrier spacing and CP length for the UL BWP.

In an example, if a bandwidth part indicator field is configured in DCIformat 1_1, the bandwidth part indicator field value may indicate anactive DL BWP, from the first set of configured DL BWPs, for DLreceptions. In an example, if a bandwidth part indicator field isconfigured in DCI format 0_1, the bandwidth part indicator field valuemay indicate an active UL BWP, from the second set of configured ULBWPs, for UL transmissions.

In an example, if a bandwidth part indicator field is configured in DCIformat 0_1 and the bandwidth part indicator field value indicates an ULBWP different from an active UL BWP, the UE may set the active UL BWP tothe UL BWP indicated by the bandwidth part indicator field in the DCIformat 01.

In an example, if a bandwidth part indicator field is configured in DCIformat 1_1 and the bandwidth part indicator field value indicates a DLBWP different from an active DL BWP, the UE may set the active DL BWP tothe DL BWP indicated by the bandwidth part indicator field in the DCIformat 1_1.

In an example, for a primary cell, a UE may be provided by a higherlayer parameter defaultDownlinkBWP-Id. In an example, the higher layerparameter defaultDownlinkBWP-Id may indicate a default DL BWP among theconfigured DL BWPs. In an example, if a UE is not provided a default DLBWP by the higher layer parameter defaultDownlinkBWP-Id, the default BWPmay be the initial active DL BWP.

In an example, a UE may be expected to detect a DCI format 0_1indicating active UL BWP change, or a DCI format 1_1 indicating activeDL BWP change, only if a corresponding PDCCH is received within first 3symbols of a slot.

In an example, for a primary cell, a UE may be provided by a higherlayer parameter Default-DL-BWP a default DL BWP among the configured DLBWPs. If a UE is not provided a default DL BWP by the higher layerparameter Default-DL-BWP, the default DL BWP is the initial active DLBWP.

In an example, if a UE is configured for a secondary cell with higherlayer parameter defaultDownlinkBWP-Id indicating a default DL BWP amongthe configured DL BWPs and the UE is configured with higher layerparameter bwp-inactivitytimer indicating a timer value, the UEprocedures on the secondary cell may be same as on a primary cell. In anexample, using the timer value for the secondary cell and the default DLBWP for the secondary cell may be same as using a timer value for theprimary cell and a default DL BWP for the primary cell.

In an example, a UE may be provided by a higher layer parameterBWP-InactivityTimer. In an example, the higher layer parameterBWP-InactivityTimer may indicate a timer with a timer value for aserving cell (e.g., primary cell, secondary cell). If configured withthe timer and the timer is running, the UE may increment the timer everyinterval of 1 millisecond for frequency range 1 or every 0.5milliseconds for frequency range 2 if the UE does not detect a DCIformat for PDSCH reception on the serving cell for paired spectrumoperation.

In an example, if configured with the timer and the timer is running,the UE may increment the timer every interval of 1 millisecond forfrequency range 1 or every 0.5 milliseconds for frequency range 2 if theUE does not detect a first DCI format for PDSCH reception or a secondDCI format for PUSCH transmission on the serving cell for unpairedspectrum operation during the interval.

In an example, if a UE is configured by a higher layer parameterfirstActiveDownlinkBWP-Id and/or a higher layer parameterfirstActiveUplinkBWP-Id. In an example, the higher layer parameterfirstActiveDownlinkBWP-Id may indicate a first active DL BWP on aserving cell (e.g., secondary cell) or on a supplementary carrier. In anexample, the wireless device may use the first active DL BWP on theserving cell as the respective first active DL BWP.

In an example, the higher layer parameter firstActiveUplinkBWP-Id mayindicate a first active UL BWP on a serving cell (e.g., secondary cell)or on a supplementary carrier. In an example, the wireless device mayuse the first active UL BWP on the serving cell or on the supplementarycarrier as the respective first active UL BWP.

In an example, for paired spectrum operation, a UE may not expect totransmit HARQ-ACK on a PUCCH resource indicated by a DCI format 1_0 or aDCI format 1_1 if the UE changes its active UL BWP on a primary cellbetween a time of a detection of the DCI format 1_0 or the DCI format1_1 and a time of a corresponding HARQ-ACK transmission on the PUCCH.

In an example, a UE may not monitor PDCCH when the UE performs RRMmeasurements over a bandwidth that is not within the active DL BWP forthe UE.

In an example, a DL BWP index (ID) may be an identifier for a DL BWP.One or more parameters in an RRC configuration may use the DL BWP-ID toassociate the one or more parameters with the DL BWP. In an example, theDL BWP ID=0 may be associated with the initial DL BWP.

In an example, an UL BWP index (ID) may be an identifier for an UL BWP.One or more parameters in an RRC configuration may use the UL BWP-ID toassociate the one or more parameters with the UL BWP. In an example, theUL BWP ID=0 may be associated with the initial UL BWP.

If a higher layer parameter firstActiveDownlinkBWP-Id is configured foran SpCell, a higher layer parameter firstActiveDownlinkBWP-Id indicatesan ID of a DL BWP to be activated upon performing the reconfiguration.

If a higher layer parameter firstActiveDownlinkBWP-Id is configured foran SCell, a higher layer parameter firstActiveDownlinkBWP-Id indicatesan ID of a DL BWP to be used upon MAC-activation of the SCell.

If a higher layer parameter firstActiveUplinkBWP-Id is configured for anSpCell, a higher layer parameter firstActiveUplinkBWP-Id indicates an IDof an UL BWP to be activated upon performing the reconfiguration.

If a higher layer parameter firstActiveUplinkBWP-Id is configured for anSCell, a higher layer parameter firstActiveUplinkBWP-Id indicates an IDof an UL BWP to be used upon MAC-activation of the SCell.

In an example, a wireless device, to execute a reconfiguration withsync, may consider an uplink BWP indicated in a higher layer parameterfirstActiveUplinkBWP-Id to be an active uplink BWP.

In an example, a wireless device, to execute a reconfiguration withsync, may consider a downlink BWP indicated in a higher layer parameterfirstActiveDownlinkBWP-Id to be an active downlink BWP.

FIG. 19 shows an example of BWP switching on a PCell.

FIG. 20 shows an example of BWP switching on an SCell.

FIG. 21A and FIG. 21B show an example of an existing random accessprocedure with BWP switching. In an example, a wireless device mayoperate on a first uplink BWP of a cell and a first downlink BWP of thecell. The wireless device may initiate a random access procedure (e.g.,contention based, contention-free) via the first uplink BWP. In anexample, if one or more PRACH occasions are not configured, by a basestation, for the first uplink BWP, the wireless device may switch fromthe first downlink BWP to an initial downlink BWP and switch from thefirst uplink BWP to an initial uplink BWP. The wireless device mayperform the random access procedure on the initial uplink BWP and theinitial downlink BWP.

In an example, a wireless device may operate on a first uplink BWP of acell and a first downlink BWP of the cell. The first uplink BWP may beidentified by a first uplink BWP specific index. The first downlink BWPmay be identified by a first downlink BWP specific index. The wirelessdevice may initiate a random access procedure (e.g., contention based,contention-free) via the first uplink BWP. In an example, if one or morePRACH occasions are configured, by a base station, for the first uplinkBWP, and if the first uplink BWP specific index is the same as the firstdownlink BWP specific index, the wireless device may perform the randomaccess procedure on the first uplink BWP and the first downlink BWP.

In an example, a wireless device may operate on a first uplink BWP of acell and a first downlink BWP of the cell. The first uplink BWP may beidentified by a first uplink BWP specific index. The first downlink BWPmay be identified by a first downlink BWP specific index. The wirelessdevice may initiate a random access procedure (e.g., contention based,contention-free) via the first uplink BWP. In an example, if one or morePRACH occasions are configured, by a base station, for the first uplinkBWP, and if the first downlink BWP specific index is different from thefirst uplink BWP specific index, the wireless device may switch from thefirst downlink BWP to a third downlink BWP of the cell with a thirddownlink BWP specific index. In an example, the third downlink BWPspecific index may be the same as the first uplink BWP specific index.In response to the switching, the wireless device may perform the randomaccess procedure on the first uplink BWP and the third downlink BWP.

In an example, the random access procedure may be contention-basedrandom access procedure. In an example, the random access procedure maybe contention-free random access procedure. In an example, the basestation and the wireless device may operate in a paired spectrum (e.g.,frequency division duplex (FDD)).

FIG. 22 shows an example flowchart of FIG. 21A and FIG. 21B.

In an example, a base station (gNB) may configure a wireless device (UE)with one or more uplink (UL) bandwidth parts (BWPs) and one or moredownlink (DL) BWPs of a cell (e.g., PCell, SCell). A first UL BWP of theone or more UL BWPs may be identified with a first UL BWP index. A firstDL BWP of the one or more DL BWPs may be identified with a first DL BWPindex.

In an example, a wireless device may operate on the first DL BWP and thefirst UL BWP. The first DL BWP and the first UL BWP may be active.

In an example, in a paired spectrum (e.g. FDD), the wireless device mayswitch the first DL BWP and the first UL BWP independently. The first ULBWP index and the first DL BWP index may be different.

In an example, in an unpaired spectrum (e.g. TDD), the wireless devicemay switch the first DL BWP and the first UL BWP simultaneously (e.g.,together). In the unpaired spectrum, the first DL BWP index and thefirst UL BWP index may be the same. In an example, the first UL BWP andthe first DL BWP may be linked (or paired) in response to the first DLBWP index and the first UL BWP index being the same.

FIG. 23 shows an example of a BWP linkage in a paired spectrum (e.g.,FDD) for a beam failure recovery (BFR) procedure. In an example, awireless device may receive one or more messages comprisingconfiguration parameters of a cell (e.g., PCell, SCell) from a basestation. In an example, the configuration parameters may comprise BWPconfiguration parameters for a plurality of DL BWPs comprising DL-BWP-1,DL-BWP-2 and DL-BWP-3 and for a plurality of UL BWPs comprisingUL-BWP-1, UL-BWP-2 and UL-BWP-3.

In an example, DL-BWP-1, DL-BWP-2 and DL-BWP-3 may be identified withDL-BWP-1 index, DL-BWP-2 index and DL-BWP-3 index (e.g., provided by ahigher layer parameter bwp-ID), respectively. In an example, UL-BWP-1,UL-BWP-2 and UL-BWP-3 may be identified with UL-BWP-1 index, UL-BWP-2index and UL-BWP-3 index (e.g., provided by a higher layer parameterbwp-ID), respectively.

In an example, the DL-BWP-1 index and UL-BWP-1 index may be the same.The DL-BWP-2 index and UL-BWP-2 index may be the same. The DL-BWP-3index and UL-BWP-3 index may be the same.

In an example, the configuration parameters may further compriseDL-BWP-specific BFR configuration parameters (e.g.,RadioLinkMonitoringConfig) for at least one of the plurality of DL BWPs(e.g., DL-BWP-1, DL-BWP-2, DL-BWP-3). In an example, the DL-BWP-specificBFR configuration parameters may be BWP specific. In an example, theDL-BWP-specific BFR configuration parameters may be BWP dedicated.

In an example, a first DL-BWP-specific BFR configuration parameters forthe DL-BWP-1 may comprise one or more first RSs (e.g.,RadioLinkMonitoringRS) of the DL-BWP-1 and a first beam failure instance(BFI) counter (e.g., beamFailureInstanceMaxCount). In an example, thewireless device may assess the one or more first RSs (e.g., SSBs,CSI-RSs) to detect a beam failure of the DL-BWP-1.

In an example, a second DL-BWP-specific BFR configuration parameters forthe DL-BWP-2 may comprise one or more second RSs (e.g.,RadioLinkMonitoringRS) of the DL-BWP-2 and a second BFI counter (e.g.,beamFailureInstanceMaxCount). In an example, the wireless device mayassess the one or more second RSs (e.g., SSBs, CSI-RSs) to detect a beamfailure of the DL-BWP-2.

In an example, the configuration parameters may further compriseUL-BWP-specific BFR configuration parameters (e.g.,BeamFailureRecoveryConfig) for at least one of the plurality of UL BWPs(e.g., UL-BWP-1, UL-BWP-2, UL-BWP-3). In an example, the UL-BWP-specificBFR configuration parameters may be BWP specific. In an example, theUL-BWP-specific BFR configuration parameters may be BWP dedicated.

In an example, a first UL-BWP-specific BFR configuration parameters forthe UL-BWP-1 may comprise one or more first candidate RSs (e.g.,candidateBeamRSList) of the DL-BWP-1 and a first search space set (e.g.,recoverySearchSpaceID) on the DL-BWP-1 in response to the DL-BWP-1 indexand UL-BWP-1 index being the same. In an example, a secondUL-BWP-specific BFR configuration parameters for the UL-BWP-2 maycomprise one or more second candidate RSs (e.g., candidateBeamRSList) ofthe DL-BWP-2 and a second search space set on the DL-BWP-2 in responseto the DL-BWP-2 index and UL-BWP-2 index being the same.

In an example, in a paired spectrum (e.g., FDD), in response to theUL-BWP-1 being configured with BFR parameters (e.g., the one or morefirst candidate RSs, the first search space set) of the DL-BWP-1, theUL-BWP-1 and the DL-BWP-1 may be linked/paired. In an example, when theDL-BWP-1 and the UL-BWP-1 are linked/paired, the DL-BWP-1 index andUL-BWP-1 index may be the same.

In an example, when the DL-BWP-1 and the UL-BWP-1 are linked, BWPswitching may be common for the DL-BWP-1 and the UL-BWP-1. In anexample, the wireless device may switch the DL-BWP-1 and the UL-BWP-1simultaneously in response to the DL-BWP-1 being linked/paired with theUL-BWP-1.

In an example, in FIG. 23, the DL-BWP-2 and the UL-BWP-2 arelinked/paired. The DL-BWP-3 and the UL-BWP3 are linked/paired.

In an example, in FIG. 23, linked BWP pairs may comprise the DL-BWP-1and the UL-BWP-1; the DL-BWP-2 and the UL-BWP-2; and the DL-BWP-3 andthe UL-BWP-3.

In an example, the wireless device may operate on at least one of theone or more linked BWPs (e.g., DL-BWP-1 and UL-BWP-1 or DL-BWP-2 andUL-BWP-2 or DL-BWP-3 and UL-BWP-3 in FIG. 23) simultaneously. In anexample, at a first time (e.g., slot), the DL-BWP-1 and the UL-BWP-1 maybe active. In an example, at a second time, DL-BWP-2 and UL-BWP-2 may beactive. In an example, at a third time, DL-BWP-3 and UL-BWP-3 may beactive.

In an example, the wireless device may operate on the UL-BWP-1 and theDL-BWP-1 simultaneously. The UL-BWP-1 and the DL-BWP-1 may be an activeUL BWP and an active DL BWP, respectively. When the wireless deviceswitches the active DL BWP from DL-BWP-1 to DL-BWP-2, the wirelessdevice may switch the active UL BWP from UL-BWP-1 to UL-BWP-2 inresponse to the DL-BWP-2 being linked to the UL-BWP-2. In an example,the switching may be response to receiving a DCI indicating a BWPswitch, or an expiry of BWP inactivity timer associated with DL-BWP-1 oran RRC signaling.

FIG. 24 shows an example embodiment. In an example, a wireless devicemay receive one or more messages comprising configuration parameters ofa cell from a base station (time T0 in FIG. 24). In an example, theconfiguration parameters may comprise BWP configuration parameters for aplurality of DL BWPs comprising DL-BWP-1, DL-BWP-2 and DL-BWP-3 and fora plurality of UL BWPs comprising UL-BWP-1, UL-BWP-2 and UL-BWP-3.

In an example, DL-BWP-1, DL-BWP-2 and DL-BWP-3 may be identified withDL-BWP-1 index, DL-BWP-2 index and DL-BWP-3 index (e.g., provided by ahigher layer parameter bwp-ID), respectively. In an example, UL-BWP-1,UL-BWP-2 and UL-BWP-3 may be identified with UL-BWP-1 index, UL-BWP-2index and UL-BWP-3 index (e.g., provided by a higher layer parameterbwp-ID), respectively.

In an example, the DL-BWP-1 index and UL-BWP-1 index may be the same.The DL-BWP-2 index and UL-BWP-2 index may be the same. The DL-BWP-3index and UL-BWP-3 index may be the same.

In an example, the configuration parameters (received at time T0 in FIG.24) may further comprise DL-BWP-specific BFR configuration parameters(e.g., RadioLinkMonitoringConfig) for at least one of the plurality ofDL BWPs (e.g., DL-BWP-1, DL-BWP-2 in FIG. 24).

In an example, the configuration parameters (received at time T0 in FIG.24) may further comprise UL-BWP-specific BFR configuration parameters(e.g., BeamFailureRecoveryConfig) for at least one of the plurality ofUL BWPs (e.g., UL-BWP-1, UL-BWP-2 in FIG. 24).

In an example, a first UL-BWP-specific BFR configuration parameters forthe UL-BWP-1 may comprise one or more first candidate RSs (e.g.,candidateBeamRSList) of the DL-BWP-1 and a first search space set (e.g.,recoverySearchSpaceID) on the DL-BWP-1 in response to the DL-BWP-1 indexand the UL-BWP-1 index being the same. In an example, a secondUL-BWP-specific BFR configuration parameters for the UL-BWP-2 maycomprise one or more second candidate RSs (e.g., candidateBeamRSList) ofthe DL-BWP-2 and a second search space set on the DL-BWP-2 in responseto the DL-BWP-2 index and the UL-BWP-2 index being the same.

In an example, in a paired spectrum (e.g., FDD), in response to theUL-BWP-1 being configured with one or more BFR parameters (e.g., the oneor more first candidate RSs, the first search space set) associated withthe DL-BWP-1, the UL-BWP-1 and the DL-BWP-1 may be linked/paired. In anexample, when the DL-BWP-1 and the UL-BWP-1 are linked/paired, theDL-BWP-1 index and UL-BWP-1 index may be the same.

In an example, in FIG. 24, the DL-BWP-2 and UL-BWP-2 are linked/pairedin response to the UL-BWP-2 being configured with one or more BFRparameters (e.g., the one or more second candidate RSs, the secondsearch space set) associated with the DL-BWP-2.

In an example, in response to the UL-BWP-3 not being configured withUL-BWP-specific BFR configuration parameters and/or the DL-BWP-3 notbeing configured with DL-BWP-specific BFR configuration parameters, theUL-BWP-3 and the DL-BWP-3 may not be linked/paired.

In an example, when the DL-BWP-3 and the UL-BWP-3 are not linked/paired,the DL-BWP-3 index and UL-BWP-3 index may be different or the same.

In an example, in FIG. 24, one or more linked BWPs may comprise theDL-BWP-1 and UL-BWP-1, and the DL-BWP-2 and UL-BWP-2.

In an example, the wireless device may activate the UL-BWP-1 and theDL-BWP-1 (time T1 in FIG. 24). In an example, the UL-BWP-1 may be anactive UL BWP and the DL-BWP-1 may be an active DL BWP in response tothe activating. The wireless device may operate on the UL-BWP-1 and theDL-BWP-1 in response to the activating.

In an example, the activating the UL-BWP-1 and the DL-BWP-1 may be inresponse to receiving a DCI or an expiry of a BWP inactivity timer or anRRC signaling. In an example, the DCI may comprise a downlink assignmenton the DL-BWP-1 and/or an uplink grant on the UL-BWP-1. In an example,the RRC signaling may indicate the UL-BWP-1 index and/or the DL-BWP-1index.

In an example, the wireless device may switch the active DL BWP from theDL-BWP-1 to the DL-BWP-2 (e.g., time T3 in FIG. 24).

In an example, the switching may be performed in response to receiving aDCI (e.g., time T2 in FIG. 24). The DCI may comprise a BWP indicatorfield. A value of the BWP indicator field may indicate the DL-BWP-2index associated with the DL-BWP-2.

In an example, the switching may be performed in response to an expiryof a BWP inactivity timer associated with the DL-BWP-1 (e.g., time T2 inFIG. 24). In an example, the DL-BWP-2 may be a default DL BWP.

In an example, the switching may be performed in response to receiving ahigher layer (e.g., RRC) parameter (firstActiveDownlinkBWP-Id) at timeT2 in FIG. 24. The higher layer parameter may indicate the DL-BWP-2index associated with the DL-BWP-2.

In an example, the wireless device may determine that the DL-BWP-2 isconfigured with DL-BWP-specific BFR configuration parameters (e.g.,RadioLinkMonitoringConfig). In response to the determining, the wirelessdevice may switch the active UL BWP from the UL-BWP-1 to the UL-BWP-2(e.g., time T3 in FIG. 24). In an example, the UL-BWP-2 index may be thesame as the DL-BWP-2 index. The UL-BWP-2 and the DL-BWP-2 may belinked/paired.

In an example, the wireless device may switch the active UL BWP from theUL-BWP-1 to the UL-BWP-2.

In an example, the switching may be performed in response to receiving aDCI. The DCI may comprise a BWP indicator field. A value of the BWPindicator field may indicate the UL-BWP-2 index associated with theUL-BWP-2.

In an example, the switching may be performed in response to receiving ahigher layer (e.g., RRC) parameter (firstActiveUplinkBWP-Id). The higherlayer parameter may indicate the UL-BWP-2 index associated with theUL-BWP-2.

In an example, the wireless device may determine that the UL-BWP-2 isconfigured with UL-BWP-specific BFR configuration parameters (e.g.,candidateBeamRSList, recoverySearchSpaceID) associated with theDL-BWP-2. In response to the determining, the wireless device may switchthe active DL BWP from the DL-BWP-1 to the DL-BWP-2. In an example, theUL-BWP-2 index may be the same as the DL-BWP-2 index. The UL-BWP-2 andthe DL-BWP-2 may be linked/paired.

FIG. 25 shows an example embodiment. The procedures at time T0 and T1 inFIG. 25 are the same as the ones in FIG. 24.

In an example, the wireless device may switch the active DL BWP from theDL-BWP-1 to the DL-BWP-3 (e.g., time T3 in FIG. 25).

In an example, the switching may be performed in response to receiving aDCI (e.g., time T2 in FIG. 25). The DCI may comprise a BWP indicatorfield. A value of the BWP indicator field may indicate the DL-BWP-3index associated with the DL-BWP-3.

In an example, the switching may be performed in response to an expiryof a BWP inactivity timer associated with the DL-BWP-1 (e.g., time T2 inFIG. 25). In an example, the DL-BWP-3 may be a default DL BWP.

In an example, the switching may be performed in response to receiving ahigher layer (e.g., RRC) parameter (firstActiveDownlinkBWP-Id) at timeT2 in FIG. 25. The higher layer parameter may indicate the DL-BWP-3index associated with the DL-BWP-3.

In an example, the wireless device may determine that the DL-BWP-3 isnot configured with DL-BWP-specific BFR configuration parameters (e.g.,RadioLinkMonitoringConfig). In response to the determining, the wirelessdevice may not switch the active UL BWP from the UL-BWP-1 to theUL-BWP-3. In an example, the UL-BWP-3 index of the UL-BWP-3 may the sameas the DL-BWP-3 index. In an example, the wireless device may maintainthe UL-BWP-1 as the active UL BWP.

FIG. 26 shows an example embodiment. The procedures at time T0 and T1 inFIG. 26 are the same as the ones in FIG. 24.

In an example, the wireless device may switch the active UL BWP from theUL-BWP-1 to the UL-BWP-3 (e.g., time T3 in FIG. 26).

In an example, the switching may be performed in response to receiving aDCI (e.g., time T2 in FIG. 26). The DCI may comprise a BWP indicatorfield. A value of the BWP indicator field may indicate the UL-BWP-3index associated with the UL-BWP-3.

In an example, the switching may be performed in response to receiving ahigher layer (e.g., RRC) parameter (firstActiveUplinkBWP-Id) at time T2in FIG. 26. The higher layer parameter may indicate the UL-BWP-3 indexassociated with the UL-BWP-3.

In an example, the UL-BWP-3 index of the UL-BWP-3 may be the same as theDL-BWP-3 index. In an example, the wireless device may determine thatthe DL-BWP-1 is configured with DL-BWP-specific BFR configurationparameters (e.g., RadioLinkMonitoringConfig). In response to thedetermining, the wireless device may switch the active DL BWP from theDL-BWP-1 to the DL-BWP-3 (e.g., time T3 in FIG. 26).

In an example, the wireless device may determine that the UL-BWP-3 isnot configured with UL-BWP-specific BFR configuration parameters (e.g.,candidateBeamRSList, recoverySearchSpaceID). In response to thedetermining, the wireless device may not switch the active DL BWP fromthe DL-BWP-1 to the DL-BWP-3. In an example, the wireless device maymaintain the DL-BWP-1 as the active DL BWP.

FIG. 27 shows a flowchart of an example embodiment.

FIG. 28 shows an example embodiment. RRC configuration at time T0 inFIG. 28 is the same as the RRC configuration at time T0 in FIG. 24. Inan example, the wireless device may activate the UL-BWP-3 and theDL-BWP-3 (e.g., time T1 in FIG. 28). In an example, the UL-BWP-3 may bean active UL BWP and the DL-BWP-3 may be an active DL BWP in response tothe activating. The wireless device may operate on the UL-BWP-3 and theDL-BWP-3 in response to the activating.

In an example, the UL-BWP-3 and the DL-BWP-3 may not be linked.

In an example, the activating the UL-BWP-3 and the DL-BWP-3 may be inresponse to receiving a DCI or an expiry of a BWP inactivity timer or anRRC signaling. In an example, the DCI may comprise a downlink assignmenton the DL-BWP-3 and/or an uplink grant on the UL-BWP-3.

In an example, the wireless device may switch the active UL BWP from theUL-BWP-3 to the UL-BWP-1 (e.g., time T3 in FIG. 28).

In an example, the switching may be performed in response to receiving aDCI (e.g., time T2 in FIG. 28). The DCI may comprise a BWP indicatorfield. A value of the BWP indicator field may indicate the UL-BWP-1index associated with the UL-BWP-1.

In an example, the switching may be performed in response to receiving ahigher layer (e.g., RRC) parameter (firstActiveUplinkBWP-Id) at time T1in FIG. 28. The higher layer parameter may indicate the UL-BWP-1 indexassociated with the UL-BWP-1.

In an example, the wireless device may determine that the DL-BWP-3 isnot configured with DL-BWP-specific BFR configuration parameters (e.g.,RadioLinkMonitoringConfig). In response to the determining, the wirelessdevice may not switch the active DL BWP from the DL-BWP-3 to theDL-BWP-1 at time T3 in FIG. 28. In an example, the wireless device maymaintain the DL-BWP-3 as the active DL BWP.

In an example, the wireless device may switch the active DL BWP from theDL-BWP-3 to the DL-BWP-1.

In an example, the switching may be performed in response to receiving aDCI. The DCI may comprise a BWP indicator field. A value of the BWPindicator field may indicate the DL-BWP-1 index associated with theDL-BWP-1.

In an example, the switching may be performed in response to an expiryof a BWP inactivity timer associated with the DL-BWP-3. In an example,the DL-BWP-1 may be a default DL BWP.

In an example, the switching may be performed in response to receiving ahigher layer (e.g., RRC) parameter (firstActiveDownlinkBWP-Id). Thehigher layer parameter may indicate the DL-BWP-1 index associated withthe DL-BWP-1.

In an example, the UL-BWP-1 index of the UL-BWP-1 may be the same as theDL-BWP-1 index. In an example, the wireless device may determine thatthe DL-BWP-1 is configured with DL-BWP-specific BFR configurationparameters (e.g., RadioLinkMonitoringConfig). In response to thedetermining, the wireless device may switch the active UL BWP from theUL-BWP-3 to the UL-BWP-1. In an example, the wireless device may set theUL-BWP-1 as the active UL BWP.

FIG. 29 shows an example embodiment. The procedures (e.g., RRCconfiguration) at time T0 in FIG. 29 is the same as ones at time T0 inFIG. 24. In an example, the wireless device may activate the UL-BWP-1and the DL-BWP-3 (time T1 in FIG. 29). In an example, the UL-BWP-1 maybe an active UL BWP and the DL-BWP-3 may be an active DL BWP in responseto the activating. The wireless device may operate on the UL-BWP-1 andthe DL-BWP-3 in response to the activating.

In an example, the activating the UL-BWP-1 and the DL-BWP-3 may be inresponse to receiving a DCI or an expiry of a BWP inactivity timer or anRRC signaling. In an example, the DCI may comprise a downlink assignmenton the DL-BWP-3 and/or an uplink grant on the UL-BWP-1.

In an example, the wireless device may switch the active DL BWP from theDL-BWP-3 to the DL-BWP-2 (e.g., time T3 in FIG. 29). In an example, thewireless device may set the DL-BWP-2 as the active DL BWP in response tothe switching.

In an example, the switching may be performed in response to receiving aDCI (e.g., time T2 in FIG. 29). The DCI may comprise a BWP indicatorfield. A value of the BWP indicator field may indicate the DL-BWP-2index associated with the DL-BWP-2.

In an example, the switching may be performed in response to an expiryof a BWP inactivity timer associated with the DL-BWP-3 at time T2 inFIG. 29. In an example, the DL-BWP-2 may be a default DL BWP.

In an example, the switching may be performed in response to receiving ahigher layer (e.g., RRC) parameter (firstActiveDownlinkBWP-Id) at timeT2 in FIG. 29. The higher layer parameter may indicate the DL-BWP-2index associated with the DL-BWP-2.

In an example, the UL-BWP-2 index of the UL-BWP-2 may be the same as theDL-BWP-2 index. In an example, the wireless device may determine thatthe DL-BWP-2 is configured with DL-BWP-specific BFR configurationparameters (e.g., RadioLinkMonitoringConfig). In response to thedetermining, the wireless device may switch the active UL BWP from theUL-BWP-1 to the UL-BWP-2. In an example, the wireless device may set theUL-BWP-2 as the active UL BWP.

In an example, the wireless device may operate on the UL-BWP-1 and theDL-BWP-3 (e.g., time T1 in FIG. 29). In an example, the wireless devicemay switch the active DL BWP from the DL-BWP-3 to a new DL-BWP of theplurality of DL BWPs. In an example, the wireless device may set the newDL-BWP as the active DL BWP in response to the switching.

In an example, the switching may be performed in response to receiving aDCI. The DCI may comprise a BWP indicator field. A value of the BWPindicator field may indicate a new DL-BWP index associated with the newDL-BWP.

In an example, the switching may be performed in response to an expiryof a BWP inactivity timer associated with the DL-BWP-3. In an example,the new DL-BWP may be a default DL BWP.

In an example, the switching may be performed in response to receiving ahigher layer (e.g., RRC) parameter (firstActiveDownlinkBWP-Id). Thehigher layer parameter may indicate the new DL-BWP index associated withthe new DL-BWP.

In an example, the wireless device may determine that the new DL-BWP isnot configured with DL-BWP-specific BFR configuration parameters (e.g.,RadioLinkMonitoringConfig). In response to the determining, the wirelessdevice may not switch the active UL BWP from the UL-BWP-1 to a newUL-BWP identified by a new UL-BWP index. The new UL-BWP index may be thesame as the new DL-BWP index.

In an example, the wireless device may maintain the UL-BWP-1 as theactive UL BWP.

In an example, the wireless device may operate on the UL-BWP-1 and theDL-BWP-3 (e.g., time T1 in FIG. 29). In an example, the wireless devicemay switch the active UL BWP from the UL-BWP-1 to a new UL-BWP of theplurality of UL BWPs. In an example, the wireless device may set the newUL-BWP as the active UL BWP in response to the switching.

In an example, the switching may be performed in response to receiving aDCI. The DCI may comprise a BWP indicator field. A value of the BWPindicator field may indicate a new UL-BWP index associated with the newUL-BWP.

In an example, the switching may be performed in response to receiving ahigher layer (e.g., RRC) parameter (firstActiveUplinkBWP-Id). The higherlayer parameter may indicate the new UL-BWP index associated with thenew UL-BWP.

In an example, the wireless device may determine that the active DL-BWP(e.g., DL-BWP-3) is not configured with DL-BWP-specific BFRconfiguration parameters (e.g., RadioLinkMonitoringConfig). In responseto the determining, the wireless device may not switch the active DL BWPfrom the DL-BWP-3 to a new DL-BWP identified by a new DL-BWP index. Inan example, the new DL-BWP index may be the same as the new UL-BWPindex.

In an example, in response to the not switching, the wireless device maymaintain the DL-BWP-3 as the active DL BWP.

In an example, the wireless device may operate on the UL-BWP-1 and theDL-BWP-3 (e.g., time T1 in FIG. 29). In an example, the wireless devicemay switch the active UL BWP from the UL-BWP-1 to the UL-BWP-2. In anexample, the wireless device may set the UL-BWP-2 as the active UL BWPin response to the switching.

In an example, the switching may be performed in response to receiving aDCI. The DCI may comprise a BWP indicator field. A value of the BWPindicator field may indicate the UL-BWP-2 index associated with theUL-BWP-2.

In an example, the switching may be performed in response to receiving ahigher layer (e.g., RRC) parameter (firstActiveUplinkBWP-Id). The higherlayer parameter may indicate the UL-BWP-2 index associated with theUL-BWP-2.

In an example, the wireless device may determine that the active DL-BWP(e.g., DL-BWP-3) is not configured with DL-BWP-specific BFRconfiguration parameters (e.g., RadioLinkMonitoringConfig). In responseto the determining, the wireless device may not switch the active DL BWPfrom the DL-BWP-3 to the DL-BWP-2. In an example, the DL-BWP-2 index maybe the same as the UL-BWP-2 index.

In an example, in response to the not switching, the wireless device maymaintain the DL-BWP-3 as the active DL BWP.

In an example, the wireless device may determine that the UL-BWP-2 isconfigured with UL-BWP-specific BFR configuration parameters (e.g.,candidateBeamRSList, recoverySearchSpaceID associated with theDL-BWP-2). In response to the determining, the wireless device mayswitch the active DL BWP from the DL-BWP-3 to the DL-BWP-2. In anexample, the DL-BWP-2 index may be the same as the UL-BWP-2 index.

In an example, in response to the switching, the wireless device may setthe DL-BWP-2 as the active DL BWP.

In an example, in FIG. 24, linked BWP pairs may comprise the DL-BWP-1and the UL-BWP-1, and the DL-BWP-2 and the UL-BWP-2. In an example, theDL-BWP-3 and the UL-BWP-3 may not be linked. In an example, when thereis at least one linked BWP pairs in a paired spectrum (e.g., FDD), thewireless device and the base station may operate as in an unpairedspectrum (e.g., TDD). In an example, BWP switching may be common for theDL-BWP-3 and the UL-BWP-3. In an example, the wireless device may switchthe DL-BWP-3 and the UL-BWP-3 simultaneously in response to being atleast one linked BWP pairs (e.g., DL-BWP-1 and UL-BWP-1 and/or DL-BWP-2and UL-BWP-2) in the paired spectrum.

In an example, a wireless device may operate on an active UL BWP of aserving cell (e.g., SCell). In an example, the wireless device mayinitiate a random access procedure on the serving cell. One or morerandom access resources (e.g., PRACH resources) may not be configuredfor the active UL BWP of the serving cell. In response to the one ormore random access resources not being configured, a MAC entity of thewireless device may switch the active UL BWP to an uplink BWP (e.g.,initial uplink BWP) of the serving cell. In an example, the uplink BWPmay be identified by an UL BWP index. In an example, the uplink BWP maybe indicated by RRC signaling (e.g., initialULBWP).

In an example, the serving cell may not be an SpCell. In an example, theserving cell may be an SCell. In an example, the uplink BWP may beconfigured with UL-BWP-specific beam failure recovery configurationparameters (e.g., candidateBeamRSList, recoverySearchSpaceID). Inresponse to the uplink BWP being configured with the UL-BWP-specific BFRconfiguration parameters, the MAC entity may switch an active DL BWP ofthe serving cell to a downlink BWP (e.g., initial downlink BWP) of theserving cell. In an example, the downlink BWP may be identified with aDL BWP index.

In an example, the serving cell may not be an SpCell. In an example, theserving cell may be an SCell. In an example, a downlink BWP (e.g.,initial downlink BWP) with a DL BWP index may be configured withDL-BWP-specific beam failure recovery (BFR) configuration parameters(e.g., RadioLinkMonitoringConfig). In an example, the downlink BWP maybe indicated by RRC signaling (e.g., initialDLBWP). In an example, theUL BWP index and the DL BWP index may be the same. In an example, inresponse to the switching the active UL BWP to the uplink BWP and thedownlink BWP being configured with the DL-BWP-specific BFR configurationparameters, the MAC entity may switch the active DL BWP to the downlinkBWP.

In an example, BWP inactivity timer associated with an active DL BWP ofplurality of DL BWPs may be configured for an activated serving cell. Inan example, a default DL BWP, of the plurality of DL BWPs, with adefault DL BWP index may be configured (e.g., via RRC signalingincluding defaultDownlinkBWP parameter) in the activated serving cell.In an example, the active DL BWP may be different from the default DLBWP.

In an example, a default UL BWP, of plurality of UL BWPs, with a defaultUL BWP index may be configured (e.g., via RRC signaling includingdefaultUplinkBWP parameter) in the activated serving cell. In anexample, an active UL BWP in the activated serving cell may be differentfrom the default UL BWP.

In an example, the BWP inactivity timer associated with the active DLBWP may expire. In response to the BWP inactivity timer expiring, a MACentity of the wireless device may perform BWP switching to the defaultDL BWP. In an example, the default DL BWP may be configured withDL-BWP-specific BFR configuration parameters (e.g.,RadioLinkMonitoringConfig). In response to the default DL BWP beingconfigured with the DL-BWP-specific BFR configuration parameters, theMAC entity may switch the active UL BWP to the default UL BWP. In anexample, the default DL BWP index may be the same as the default UL BWPindex.

In an example, BWP inactivity timer associated with an active DL BWP maybe configured for an activated serving cell. In an example, a default DLBWP may not be configured in the activated serving cell. In an example,the active DL BWP may be different from an initial downlink BWP (e.g.,configured via RRC signaling including initiaIDownlinkBWP parameter)with an initial downlink BWP index.

In an example, an initial uplink BWP with an initial uplink BWP indexmay be configured (e.g., via RRC signaling including initialUplinkBWPparameter) in the activated serving cell. In an example, an active ULBWP may be different from the initial uplink BWP.

In an example, the BWP inactivity timer associated with the active DLBWP may expire. In response to the BWP inactivity timer expiring and thedefault DL BWP not being configured, a MAC entity of the wireless devicemay switch from the active DL BWP to the initial downlink BWP.

In an example, the initial downlink BWP may be configured withDL-BWP-specific BFR configuration parameters (e.g.,RadioLinkMonitoringConfig). In response to the initial downlink beingconfigured with the DL-BWP-specific BFR configuration parameters, theMAC entity may switch the active UL BWP to the initial uplink BWP. In anexample, the initial downlink BWP index may be the same as the initialuplink BWP index.

In an example, a wireless device may receive, from a base station, oneor more configuration parameters (e.g. RRC connection reconfigurationmessage, or RRC connection reestablishment message, or RRC connectionsetup message). The one or more configuration parameters may compriserespective downlink bandwidth part (BWP) specific index for eachdownlink BWP of downlink BWPs and respective uplink BWP specific indexfor each uplink BWP of uplink BWPs.

In an example, each uplink BWP of the uplink BWPs may be in one of anactive state and an inactive state. In an example, the active state of afirst uplink BWP of the uplink BWPs may comprise transmitting a firstuplink signal (e.g., PUCCH, PUSCH, SRS, etc.) via the first uplink BWP.In an example, the inactive state of the first uplink BWP may comprisenot transmitting a first uplink signal (e.g., PUCCH, PUSCH, SRS etc.)via the first uplink BWP.

In an example, each downlink BWP of the downlink BWPs may be in one ofan active state and an inactive state. In an example, the active stateof a first downlink BWP of the downlink BWPs may comprise monitoring adownlink control channel of the first downlink BWP. In an example, theinactive state of the first downlink BWP may comprise not monitoring adownlink control channel of the first downlink BWP.

In an example, the wireless device may activate a first downlink BWP ofthe downlink BWPs as an active downlink BWP. The first downlink BWP maybe identified by a first downlink BWP index. In an example, the wirelessdevice may activate, in a second slot, a first uplink BWP of the uplinkBWPs as an active uplink BWP. The first uplink BWP may be identified bya first uplink BWP index.

In an example, the first slot and the second slot may be the same.

In an example, the first slot and the second slot may be different.

In an example, the wireless device may set/switch the active downlinkBWP from the first downlink BWP to a second downlink BWP of the downlinkBWPs. The second downlink BWP may be identified by a second downlink BWPindex.

In an example, the wireless device may receive, on the first downlinkBWP, a downlink control information (DCI) with a BWP indicator field.The BWP indicator field may indicate a second downlink BWP index of asecond downlink BWP of the downlink BWPs. In an example, the wirelessdevice may set/switch the active downlink BWP from the first downlinkBWP to the second downlink BWP in response to the BWP indicator fieldindicating the second downlink BWP index.

In an example, the wireless device may receive, on the first downlinkBWP, a higher layer parameter (e.g., RRC message). The higher layerparameter may indicate a second downlink BWP index of a second downlinkBWP of the downlink BWPs. In an example, the wireless device mayset/switch the active downlink BWP from the first downlink BWP to thesecond downlink BWP in response to the higher layer parameter indicatingthe second downlink BWP index.

In an example, a BWP inactivity timer associated with the first downlinkBWP may expire. The wireless device may set/switch the active downlinkBWP from the first downlink BWP to a second downlink BWP of the downlinkBWPs in response to the BWP inactivity timer expiring. In an example,the second downlink BWP may be a default DL BWP. The second downlink BWPmay be identified by a second downlink BWP index.

In an example, the one or more configuration parameters may furthercomprise DL-BWP-specific beam failure recovery (BFR) configurationparameters. In an example, the DL-BWP-specific BFR configurationparameters may comprise a first set of reference signal (RS) resourceconfigurations for the second downlink BWP. The first set of RS resourceconfigurations may comprise one or more first RSs (e.g., CSI-RS or SSblocks) of the second downlink BWP.

In an example, the wireless device may monitor at least one PDCCH of thesecond downlink BWP. At least one RS (e.g., DM-RS) of the at least onePDCCH may be associated (e.g., QCLed) with the one or more first RSs.

In an example, the wireless device may determine that the seconddownlink BWP is configured with the DL-BWP-specific BFR configurationparameters (e.g., one or more first RSs used inRadioLinkMonitoringConfig).

In an example, in response to the determining, the wireless device mayswitch an active uplink BWP from the first uplink BWP to a second uplinkBWP of the uplink BWPs. The second uplink BWP may be identified by asecond uplink BWP index. In an example, the second uplink BWP index maybe the same as the second downlink BWP index.

In an example, the wireless device may determine that the seconddownlink BWP is not configured with the DL-BWP-specific BFRconfiguration parameters (e.g., one or more first RSs used inRadioLinkMonitoringConfig).

In an example, in response to the determining, the wireless device maynot switch the active uplink BWP from the first uplink BWP to a seconduplink BWP of the uplink BWPs. The second uplink BWP may be identifiedby a second uplink BWP index. In an example, the second uplink BWP indexmay be the same as the second downlink BWP index.

In an example, in response to the determining that the second downlinkBWP is not configured with the DL-BWP-specific BFR configurationparameters, the wireless device may keep the first uplink BWP as theactive uplink BWP.

In an example, the wireless device may set/switch the active uplink BWPfrom the first uplink BWP to a second uplink BWP of the uplink BWPs. Thesecond uplink BWP may be identified by a second uplink BWP index.

In an example, the setting/switching may be triggered in response toreceiving a downlink control information (DCI) with a BWP indicatorfield. The BWP indicator field may indicate the second uplink BWP index.

In an example, the setting/switching may be triggered in response toreceiving a higher layer parameter (e.g., RRC message). The higher layerparameter may indicate the second uplink BWP index.

In an example, the wireless device may determine that the second uplinkBWP is configured with UL-BWP-specific BFR configuration parameters(e.g., candidateBeamRSList, recoverySearchSpaceID).

In an example, in response to the determining, the wireless device mayswitch an active downlink BWP from the first downlink BWP to a seconddownlink BWP of the downlink BWPs. The second downlink BWP may beidentified by a second downlink BWP index. In an example, the seconduplink BWP index may be the same as the second downlink BWP index.

In an example, the wireless device may determine that the second uplinkBWP is not configured with UL-BWP-specific BFR configuration parameters(e.g., candidateBeamRSList, recoverySearchSpaceID).

In an example, in response to the determining, the wireless device maynot switch the active downlink BWP from the first downlink BWP to asecond downlink BWP of the downlink BWPs. The second downlink BWP may beidentified by a second downlink BWP index. In an example, the seconduplink BWP index may be the same as the second downlink BWP index.

In an example, in response to the determining that the second uplink BWPis not configured with UL-BWP-specific BFR configuration parameters, thewireless device may keep the first downlink BWP as the active downlinkBWP.

In an example, the wireless device may determine that the first downlinkBWP is configured with the DL-BWP-specific BFR configuration parameters(e.g., one or more first RS s used in RadioLinkMonitoringConfig). In anexample, in response to the determining, the wireless device may switchthe active downlink BWP from the first downlink BWP to a second downlinkBWP of the downlink BWPs. The second downlink BWP may be identified by asecond downlink BWP index. In an example, the second uplink BWP indexmay be the same as the second downlink BWP index.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of base stations or a plurality ofwireless devices in a coverage area that may not comply with thedisclosed methods, for example, because those wireless devices or basestations perform based on older releases of LTE or 5G technology.

In an example, a wireless device may be configured with beam failurerecovery (BFR) parameters. The BFR parameters may comprise one or morefirst reference signals for beam failure detection for an activedownlink BWP of a cell. The BFR parameters may comprise one or moresecond reference signals for candidate beam selection for an activeuplink BWP of the cell. The wireless device may measure the one or moresecond reference signals for a beam failure recovery procedure of theactive downlink BWP.

In existing systems, when a wireless device is configured with BFRparameters, the wireless device may operate (or be active) on linkedBWPs (e.g., BWP linkage). The operating (or being active) on the linkedBWPs may comprise that the wireless device may activate a downlink BWPand an uplink BWP with the same BWP indices. For example, the wirelessdevice may be active, e.g., simultaneously, on a downlink BWP identifiedwith a downlink BWP index and on an uplink BWP identified with an uplinkBWP index that is the same as the downlink BWP index.

In an example, a base station may not configure each BWP of a cell withBFR parameters. Configuring each BWP of the cell with the BFR parametersmay increase the resource overhead and/or power consumption at thewireless device (to monitor the reference signals for beam failuredetection and/or candidate beam identification).

Implementation of existing BWP linkage when a wireless device isconfigured with BFR parameters may not be efficient when a BWP (or notall BWPs) of a cell is not configured with BFR parameters. In anexample, the BWP linkage may reduce flexibility. The base station maynot switch, the wireless device, to unlinked BWPs (e.g., BWPs withdifferent BWP indices) when the unlinked BWPs have better channelquality. There is a need to implement an enhanced procedure for BWPlinkage when a BWP (or not all BWPs) of a cell is not configured withBFR parameters.

Example embodiments implement an enhanced procedure for BWP linkage whena BWP (or not all BWPs) of a cell is not configured with BFR parameters.In an example, a wireless device may switch an active downlink BWP of acell to a downlink BWP. If the wireless device determines that thedownlink BWP is configured with BFR parameters, the wireless device mayswitch an active uplink BWP of the cell to an uplink BWP linked to thedownlink BWP. If the wireless device determines that the downlink BWP isnot configured with BFR parameters, the wireless device may keep anactive uplink BWP of the cell (e.g., no uplink BWP switching). Thewireless device may determine BWP switching to a linked BWP based on theswitched BWP is configured with BFR parameters or not.

This enhanced process improves flexibility. In an example, the basestation may schedule the wireless device via unlinked BWPs. Thisenhanced process reduces BWP switching delay reducing interruptions inuplink transmission and/or downlink receptions.

According to various embodiments, a device such as, for example, awireless device, a base station, and/or the like, may comprise one ormore processors and memory. The memory may store instructions that, whenexecuted by the one or more processors, cause the device to perform aseries of actions. Embodiments of example actions are illustrated in theaccompanying figures and specification. Features from variousembodiments may be combined to create yet further embodiments.

FIG. 30 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 3010, a wireless device may switch from afirst downlink BWP to a second downlink BWP. At 3020, a determinationmay be made that the second downlink BWP is configured with one or morebeam failure recovery (BFR) parameters. At 3030, based on thedetermining, a first uplink BWP may be switched to a second uplink BWP.At 3040, a switch may be made from the second downlink BWP to a thirddownlink BWP. At 3050, it may be determined that the third downlink BWPis not configured with one or more BFR parameters. At 3060, based on thedetermining that the third downlink BWP is not configured with the oneor more BFR parameters, the second uplink BWP may be kept as an activeuplink BWP.

In an example, a wireless device may activate a first downlink bandwidthpart (BWP) of a cell and a first uplink BWP of the cell. The wirelessdevice may switch from the first downlink BWP to a second downlink BWPas an active downlink BWP. The second downlink BWP may be identifiedwith a second downlink BWP index. A determination may be made that thesecond downlink BWP is configured with one or more beam failure recovery(BFR) parameters. Based on the determination, the first uplink BWP maybe switched to a second uplink BWP as an active uplink BWP. The seconduplink BWP may be identified with a second uplink BWP index that is thesame as the second downlink BWP index. The second downlink BWP may beswitched to a third downlink BWP as an active downlink BWP. Adetermination may be made that the third downlink BWP is not configuredwith one or more BFR parameters. Based on the determination that thethird downlink BWP is not configured with the one or more BFRparameters, the second uplink BWP may be kept as an active uplink BWP.

According to an example embodiment, the wireless device may activate thefirst downlink BWP in a first slot. According to an example embodiment,the wireless device may activate the first uplink BWP in a second slot.According to an example embodiment, the first slot and the second slotmay be the same. According to an example embodiment, the first slot andthe second slot may be different.

According to an example embodiment, the switching from the firstdownlink BWP to the second downlink BWP may comprise activating thesecond downlink BWP. According to an example embodiment, the switchingfrom the first downlink BWP to the second downlink BWP may comprisedeactivating the first downlink BWP. According to an example embodiment,the deactivating of a first downlink BWP may comprise not monitoring adownlink control channel of the first downlink BWP.

According to an example embodiment, the one or more BFR parameters for adownlink BWP may indicate one or more reference signals for beam failuredetection of the downlink BWP the cell. According to an exampleembodiment, the wireless device may activate a first downlink BWP of thecell and a first uplink BWP of the cell. The wireless device may switchfrom the first uplink BWP to a second uplink BWP as an active uplinkBWP. The second uplink BWP may be identified with a second uplink BWPindex. According to an example embodiment, the wireless device maydetermine that the second uplink BWP is configured with one or moresecond BFR parameters. Based on the determining, the wireless device mayswitch from the first downlink BWP to a second downlink BWP as an activedownlink BWP. The second downlink BWP may be identified with a seconddownlink BWP index that is the same as the second uplink BWP index.According to an example embodiment, the wireless device may determinethat the second uplink BWP is not configured with one or more second BFRparameters. Based on the determining, the wireless device may keep thefirst downlink BWP as an active downlink BWP. According to an exampleembodiment, the one or more second BFR parameters may comprise one ormore second reference signals for candidate beam selection of the cell.

According to an example embodiment, the activating a first downlink BWPmay comprise monitoring a downlink control channel of the first downlinkBWP. According to an example embodiment, the activating a first uplinkBWP may comprise transmitting an uplink signal via the first uplink BWP.

According to an example embodiment, the wireless device may receive oneor more configuration parameters for downlink BWPs and uplink BWPs.According to an example embodiment, the downlink BWPs may comprise thefirst downlink BWP, the second downlink BWP and the third downlink BWP.According to an example embodiment, the uplink BWPs may comprise thefirst uplink BWP and the second uplink BWP. According to an exampleembodiment, the one or more configuration parameters may furtherindicate downlink BWP specific indexes for the downlink BWPs. The one ormore configuration parameters may further indicate uplink BWP specificindexes for the uplink BWPs. According to an example embodiment, thedownlink BWP indexes may comprise the second downlink BWP index. Theuplink BWP indexes may comprise the second uplink BWP index.

A wireless device may switch from a first downlink BWP to a seconddownlink BWP. The second downlink BWP may be identified with a seconddownlink BWP index. A determination may be made that the second downlinkBWP is configured with one or more beam failure recovery (BFR)parameters. Based on the determination, a first uplink BWP may beswitched to a second uplink BWP. The second uplink BWP may be identifiedwith a second uplink BWP index that is the same as the second downlinkBWP index. The second downlink BWP may be switched to a third downlinkBWP. A determination may be made that the third downlink BWP is notconfigured with one or more BFR parameters. Based on the determinationthat the third downlink BWP is not configured with the one or more BFRparameters, the second uplink BWP may be kept as an active uplink BWP.

A wireless device may receive one or more configuration parameters fordownlink bandwidth parts (BWPs) and uplink BWPs. A first downlink BWP ofthe downlink BWPs may be activated as an active downlink BWP. A firstuplink BWP of the uplink BWPs may be activated as an active uplink BWP.The active downlink BWP may be switched from the first downlink BWP to asecond downlink BWP of the downlink BWPs. The second downlink BWP may beidentified with a second downlink BWP index. A determination may be madethat the second downlink BWP is configured with one or more beam failurerecovery (BFR) parameters. Based on the determination, the active uplinkBWP may be switched from the first uplink BWP to a second uplink BWP ofthe uplink BWPs. The second uplink BWP may be identified with a seconduplink BWP index that is the same as the second downlink BWP index.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed to one or more of the various embodiments.

If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state

In this disclosure, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more messagescomprise a plurality of parameters, it implies that a parameter in theplurality of parameters is in at least one of the one or more messages,but does not have to be in each of the one or more messages.

Furthermore, many features presented above are described as beingoptional through the use of “may” or the use of parentheses. For thesake of brevity and legibility, the present disclosure does notexplicitly recite each and every permutation that may be obtained bychoosing from the set of optional features. However, the presentdisclosure is to be interpreted as explicitly disclosing all suchpermutations. For example, a system described as having three optionalfeatures may be embodied in seven different ways, namely with just oneof the three possible features, with any two of the three possiblefeatures or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (i.e.hardware with a biological element) or a combination thereof, all ofwhich may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally, it may be possible to implement modules using physicalhardware that incorporates discrete or programmable analog, digitaland/or quantum hardware. Examples of programmable hardware comprise:computers, microcontrollers, microprocessors, application-specificintegrated circuits (ASICs); field programmable gate arrays (FPGAs); andcomplex programmable logic devices (CPLDs). Computers, microcontrollersand microprocessors are programmed using languages such as assembly, C,C++ or the like. FPGAs, ASICs and CPLDs are often programmed usinghardware description languages (HDL) such as VHSIC hardware descriptionlanguage (VHDL) or Verilog that configure connections between internalhardware modules with lesser functionality on a programmable device. Theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the scope. In fact, after reading the abovedescription, it will be apparent to one skilled in the relevant art(s)how to implement alternative embodiments. Thus, the present embodimentsshould not be limited by any of the above described exemplaryembodiments.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: switching, by a wirelessdevice, from a first downlink bandwidth part (BWP) to a second downlinkBWP identified with a downlink BWP index; based on the second downlinkBWP being configured with beam failure recovery (BFR), switching from afirst uplink BWP to a second uplink BWP identified with an uplink BWPindex that is the same as the downlink BWP index; switching from thesecond downlink BWP to a third downlink BWP; and based on the thirddownlink BWP not being configured with BFR, keeping the second uplinkBWP as an active uplink BWP.
 2. The method of claim 1, furthercomprising activating the first downlink BWP in a first slot.
 3. Themethod of claim 2, further comprising activating the first uplink BWP ina second slot.
 4. The method of claim 3, wherein the first slot and thesecond slot are the same.
 5. The method of claim 1, wherein theswitching from the first downlink BWP to the second downlink BWPcomprises activating the second downlink BWP.
 6. The method of claim 1,wherein the switching from the first downlink BWP to the second downlinkBWP comprises deactivating the first downlink BWP.
 7. The method ofclaim 6, wherein the deactivating the first downlink BWP comprises notmonitoring a downlink control channel of the first downlink BWP.
 8. Themethod of claim 1, further comprising: activating the first downlink BWPand the first uplink BWP; and second switching from the first uplink BWPto the second uplink BWP, as the active uplink BWP, identified with theuplink BWP index.
 9. The method of claim 8, further comprising:determining that the second uplink BWP is configured with one or moresecond BFR parameters; and switching, based on the second switching andthe determining that the second uplink BWP is configured with one ormore second BFR parameters, from the first downlink BWP to the seconddownlink BWP, as an active downlink BWP, identified with a seconddownlink BWP index that is the same as the uplink BWP index.
 10. Themethod of claim 8, further comprising: determining that the seconduplink BWP is not configured with one or more second BFR parameters; andkeeping, based on the second switching and the determining that thesecond uplink BWP is not configured with one or more second BFRparameters, the first downlink BWP as an active downlink BWP.
 11. Awireless device comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe wireless device to: switch from a first downlink bandwidth part(BWP) to a second downlink BWP identified with a downlink BWP index;based on the second downlink BWP being configured with beam failurerecovery (BFR), switch from a first uplink BWP to a second uplink BWPidentified with an uplink BWP index that is the same as the downlink BWPindex; switch from the second downlink BWP to a third downlink BWP; andbased on the third downlink BWP not being configured with BFR, keep thesecond uplink BWP as an active uplink BWP.
 12. The wireless device ofclaim 11, wherein the instructions, when executed by the one or moreprocessors, further cause the wireless device to activate the firstdownlink BWP in a first slot.
 13. The wireless device of claim 12,wherein the instructions, when executed by the one or more processors,further cause the wireless device to activate the first uplink BWP in asecond slot.
 14. The wireless device of claim 13, wherein the first slotand the second slot are the same.
 15. The wireless device of claim 11,wherein the switch from the first downlink BWP to the second downlinkBWP comprises activating the second downlink BWP.
 16. The wirelessdevice of claim 11, wherein the switch from the first downlink BWP tothe second downlink BWP comprises deactivating the first downlink BWP.17. The wireless device of claim 16, wherein the deactivation of thefirst downlink BWP comprises not monitoring a downlink control channelof the first downlink BWP.
 18. The wireless device of claim 11, whereinthe instructions, when executed by the one or more processors, furthercause the wireless device to: activate the first downlink BWP and thefirst uplink BWP; and second switch from the first uplink BWP to thesecond uplink BWP, as the active uplink BWP, identified with the uplinkBWP index.
 19. The wireless device of claim 18, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to: determine that the second uplink BWP isconfigured with one or more second BFR parameters; and switch, based onthe second switching and the determination that the second uplink BWP isconfigured with one or more second BFR parameters, from the firstdownlink BWP to the second downlink BWP, as an active downlink BWP,identified with a second downlink BWP index that is the same as theuplink BWP index.
 20. A system comprising: a base station; comprising:one or more first processors; and first memory storing firstinstructions that, when executed by the one or more first processors,cause the base station to transmit beam failure recovery (BFR)parameters; and a wireless device comprising: one or more secondprocessors; and second memory storing second instructions that, whenexecuted by the one or more second processors, cause the wireless deviceto: receive the beam failure recovery (BFR) parameters; switch from afirst downlink bandwidth part (BWP) to a second downlink BWP identifiedwith a downlink BWP index; based on the second downlink BWP beingconfigured with the BFR parameters, switch from a first uplink BWP to asecond uplink BWP identified with an uplink BWP index that is the sameas the downlink BWP index; switch from the second downlink BWP to athird downlink BWP; and based on the third downlink BWP not beingconfigured with the BFR parameters, keep the second uplink BWP as anactive uplink BWP.